User interface for loyalty accounts and private label accounts for a wearable device

ABSTRACT

The present disclosure generally relates to the use of loyalty accounts, private label payment accounts, and general payment accounts using a wearable electronic device with an electronic wallet. Various accounts are linked to the electronic device. In some examples, the electronic device is NFC-enabled. The electronic device may be used to provide loyalty account information and payment account information to a payment terminal, such as an NFC-enabled payment terminal.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/192,409, entitled “USER INTERFACE FOR LOYALTY ACCOUNTS AND PRIVATELABEL ACCOUNTS FOR A WEARABLE DEVICE”, filed Mar. 4, 2021, which is acontinuation of U.S. patent application Ser. No. 14/870,793, now U.S.Pat. No. 10,990,934, entitled “USER INTERFACE FOR LOYALTY ACCOUNTS ANDPRIVATE LABEL ACCOUNTS FOR A WEARABLE DEVICE”, filed Sep. 30, 2015,which is a continuation of U.S. patent application Ser. No. 14/869,877,entitled “USER INTERFACE FOR LOYALTY ACCOUNTS AND PRIVATE LABEL ACCOUNTSFOR A WEARABLE DEVICE”, filed Sep. 29, 2015, which claims priority fromU.S. Provisional Patent Application Ser. No. 62/230,430, entitled “USERINTERFACE FOR LOYALTY ACCOUNTS AND PRIVATE LABEL ACCOUNTS FOR A WEARABLEDEVICE”, filed Jun. 5, 2015, which is hereby incorporated by referencein its entirety for all purposes.

This application relates to the following provisional applications: U.S.Patent Application Ser. No. 62/004,886, entitled “USER INTERFACE FORPAYMENTS”, filed May 29, 2014, (Reference No. P22848USP1); U.S. PatentApplication Ser. No. 62/047,545, entitled “USER INTERFACE FOR PAYMENTS”,filed Sep. 8, 2014, (Reference No. P22848USP2); U.S. Patent ApplicationSer. No. 62/127,790, entitled “USER INTERFACE FOR PAYMENTS”, filed Mar.3, 2015, (Reference No. P22848USP3); and U.S. Patent Application Ser.No. 62/110,566, entitled “USER INTERFACE FOR PAYMENTS”, filed Feb. 1,2015, (Reference No. P26049USP1); U.S. Patent Application Ser. No.61/912,727, entitled “PROVISIONING AND AUTHENTICATING CREDENTIALS ON ANELECTRONIC DEVICE”, filed Dec. 6, 2013, (Reference No. P19543USP1); U.S.Patent Application Ser. No. 61/909,717, entitled “PROVISIONING OFCREDENTIALS ON AN ELECTRONIC DEVICE USING PASSWORDS COMMUNICATED OVERVERIFIED CHANNELS”, filed Nov. 27, 2013, (Reference No. P19950USP1);U.S. Patent Application Ser. No. 62/004,182, entitled “ONLINE PAYMENTSUSING A SECURE ELEMENT OF AN ELECTRONIC DEVICE”, filed May 28, 2014,(Reference No. P20450USP4); U.S. Patent Application Ser. No. 61/920,029,entitled “DELETION OF CREDENTIALS FROM AN ELECTRONIC DEVICE”, filed Dec.23, 2013, (Reference No. P21084USP1); U.S. Patent Application Ser. No.61/899,737, entitled “USING BIOAUTHENTICATION INNEAR-FIELD-COMMUNICATION TRANSACTIONS”, filed Nov. 4, 2013, (ReferenceNo. P21646USP1); U.S. Patent Application Ser. No. 61/905,035, entitled“GENERATING TRANSACTION IDENTIFIERS”, filed Nov. 15, 2013, (ReferenceNo. P21714USP1); U.S. Patent Application Ser. No. 61/905,042, entitled“ELECTRONIC RECEIPTS FOR NFC-BASED FINANCIAL TRANSACTIONS”, filed Nov.15, 2013, (Reference No. 21734USP1); U.S. Patent Application Ser. No.62/004,798, entitled “FINANCIAL-TRANSACTION NOTIFICATIONS”, filed May29, 2014, (Reference No. P23211USP1); U.S. Patent Application Ser. No.62/004,837, entitled “METHODS FOR MANAGING PAYMENT APPLETS ON A SECUREELEMENT TO CONDUCT MOBILE PAYMENT TRANSACTIONS”, filed May 29, 2014,(Reference No. P23215USP1); U.S. Patent Application Ser. No. 62/004,840,entitled “METHODS FOR OPERATING A PORTABLE ELECTRONIC DEVICE TO CONDUCTMOBILE PAYMENT TRANSACTIONS”, filed May 29, 2014, (Reference No.P23223USP1); U.S. Patent Application Ser. No. 62/004,835, entitled“METHODS FOR USING A PRIMARY USER DEVICE TO PROVISION CREDENTIALS ONTO ASECONDARY USER DEVICE”, filed May 29, 2014, (Reference No. P23224USP1);U.S. Patent Application Ser. No. 62/004,832, entitled “METHODS FOR USINGA RANDOM AUTHORIZATION NUMBER TO PROVIDE ENHANCED SECURITY FOR A SECUREELEMENT”, filed May 29, 2014, (Reference No. P23261USP1); U.S. PatentApplication Ser. No. 62/004,338, entitled “USER DEVICE SECUREPARTICIPATION IN TRANSACTIONS VIA LOCAL SECURE ELEMENT DETECTION OFMECHANICAL INPUT”, filed May 29, 2014, (Reference No. P22931USP1); andU.S. Utility patent application Ser. No. 14/092,205, entitled “SECUREPROVISIONING OF CREDENTIALS ON AN ELECTRONIC DEVICE”, filed Nov. 27,2013, (Reference No. P19545US1); each of which is hereby incorporated byreference in its entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for computer user interfaces forloyalty accounts and payment accounts.

BACKGROUND

The use of electronic devices for making payments at point-of-saleterminals and over the Internet has increased significantly in recentyears. Exemplary point-of-sale terminals include Near FieldCommunication-enabled (NFC-enabled) terminals, bluetooth-enabledterminals, and barcode scanner-enabled terminals. Electronic devices canbe used in conjunction with these exemplary terminals to enable the userof the electronic device to make a payment for the purchase of, forexample, a good or service.

BRIEF SUMMARY

Some techniques for linking accounts to an electronic device, selectingan account for use in a transaction, and transmitting accountinformation in a transaction, however, are generally cumbersome andinefficient. For example, existing techniques use a complex andtime-consuming user interface, which may include multiple key presses orkeystrokes. Existing techniques require more time than necessary,wasting user time and device energy. This latter consideration isparticularly important in battery-operated devices.

Accordingly, the present inventions provide for electronic devices withfaster, more efficient methods and interfaces for linking accounts to anelectronic device, selecting an account for use in a transaction, andtransmitting account information in a transaction. Such methods andinterfaces optionally complement or replace other methods for performingsimilar tasks. Such methods and interfaces reduce the cognitive burdenon a user and produce a more efficient human-machine interface. Suchmethods and interfaces may also reduce the number of unnecessary,extraneous, repetitive, and/or redundant inputs, and may create a fasterand more efficient user interface arrangement, which may reduce thenumber of required inputs, reduce processing power, and reduce theamount of time for which user interfaces need to be displayed in orderfor desired functions to be accessed and carried out. Forbattery-operated computing devices, such methods and interfaces conservepower and increase the time between battery charges.

A method, comprising: at an electronic device with a display, atouch-sensitive surface, and one or more wireless communicationelements: receiving an input requesting to enable the device for apayment transaction; in response to receiving the input requesting toenable the device for a payment transaction: displaying, on the display,a first visual indicator identifying a first account; and enabling theelectronic device to participate in a transaction using the firstaccount via the one or more wireless communication elements; receivingone or more swipe inputs in a first direction via the touch-sensitivesurface; in response to receiving the one or more user swipe inputs:displaying, on the display, a second visual indicator identifying asecond account; and enabling the electronic device to participate in atransaction using the second account via the one or more wirelesscommunication elements; and wherein the first visual indicator isdifferent from the second visual indicator.

A method, comprising: at an electronic device with a display and alocation sensor: detecting, using the location sensor, a currentlocation; determining whether the current location is associated with afirst account; in accordance with a failure to determine that thecurrent location is associated with an account other than a defaultpayment account, displaying, on the display, a visual indication of adefault payment account; in accordance with a determination that thecurrent location is associated with the first account, concurrentlydisplaying, on the display, the visual indication of the default paymentaccount and a visual indication of the first account; and wherein thedefault payment account and the first account are linked to theelectronic device and the default payment account and the first accountare different.

A method, comprising: at an electronic device with a display and alocation sensor: receiving an input requesting to enable the device fora payment transaction; and in response to receiving the input:detecting, using the location sensor, a current location; determiningwhether a set of one or more payment criteria have been met, wherein theset of one or more payment criteria includes a criterion that is metwhen the current location is associated with a first payment account; inaccordance with a determination that the set of one or more paymentcriteria is not met, displaying, on the display, a visual indication ofa default payment account, wherein the default payment account isdifferent from the first payment account; and in accordance with adetermination that the set of one or more payment criteria is met,displaying, on the display, a visual indication of the first paymentaccount.

A method, comprising: at an electronic device with a display and one ormore wireless communication elements: receiving an input requesting toenable the device for a payment transaction; in response to receivingthe input, displaying, on the display, a payment indication thatrepresents a plurality of payment accounts including a first paymentaccount and a second payment account; receiving, via the one or morewireless communication elements, a request for account informationcorresponding to a payment transaction; in response to receiving therequest for account information corresponding to the paymenttransaction: in accordance with a determination that payment criteriafor a first payment account have been met, transmitting, via the one ormore wireless communication elements, account information for the firstpayment account without transmitting account information for the secondpayment account; and in accordance with a determination that paymentcriteria for the second payment account have been met, transmitting, viathe one or more wireless communication elements, account information forthe second payment account without transmitting account information forthe first payment account.

A method, comprising: at an electronic device with a display, atouch-sensitive surface configured to detect intensity of contacts, andone or more wireless communication elements: receiving a first input; inresponse to receiving the first input: displaying, on the display, afirst user interface, wherein the first user interface includes: a firstvisual indicator identifying a payment card associated with multiplepayment accounts, and a second visual indicator identifying a firstpayment account of the multiple payment accounts of the payment card;enabling the electronic device to use the first payment account toengage in a payment transaction via the one or more wirelesscommunication elements; detecting a first contact on the touch-sensitivesurface; determining whether a characteristic intensity of the firstcontact is above an intensity threshold; and in accordance with adetermination that the characteristic intensity of the first contact isabove the intensity threshold, displaying, on the display, a second userinterface, wherein the second user interface enables selection betweendifferent payment accounts represented by the first visual indicator.

A method, comprising: at a first electronic device with a display andone or more wireless communication elements: receiving a first requestto link a payment account associated with a payment card to the firstelectronic device; in response to receiving the first request,initiating a process for linking the payment account to the firstelectronic device; after successfully linking the payment account to thefirst electronic device, concurrently displaying, on the display: anindication that the payment account has been successfully linked to thefirst electronic device; and a selectable affordance for linking thepayment account to a second electronic device different from the firstelectronic device; and receiving activation of the selectableaffordance; and in response to receiving activation of the selectableaffordance, initiating a process for linking the payment account to thesecond electronic device.

A method, comprising: at a first electronic device with a display andone or more wireless communication elements: displaying, on the display,a payment-account user interface for a second electronic device that isassociated with the first electronic device, wherein displaying thepayment-account user interface includes concurrently displaying: arepresentation of a first payment account along with status informationfor the first payment account indicating that the first payment accountis linked to the second electronic device and that the second electronicdevice is configured to enable payment using the first payment account;and a representation of a second payment account along with statusinformation for the second payment account indicating that the secondpayment account is linked to the first electronic device but is notlinked to the second electronic device.

An electronic device, comprising: a display; a touch-sensitive surface;and means for receiving an input requesting to enable the device for apayment transaction; means, responsive to receiving the input requestingto enable the device for a payment transaction, for: displaying, on thedisplay, a first visual indicator identifying a first account; andenabling the electronic device to participate in a transaction using thefirst account via the one or more wireless communication elements; meansfor receiving one or more swipe inputs in a first direction via thetouch-sensitive surface; means, response to receiving the one or moreuser swipe inputs, for: displaying, on the display, a second visualindicator identifying a second account; and enabling the electronicdevice to participate in a transaction using the second account via theone or more wireless communication elements; and wherein the firstvisual indicator is different from the second visual indicator.

An electronic device, comprising: a display; a touch-sensitive surface;and means for detecting, using the location sensor, a current location;means for determining whether the current location is associated with afirst account; means, in accordance with a failure to determine that thecurrent location is associated with an account other than a defaultpayment account, for displaying, on the display, a visual indication ofa default payment account; means, in accordance with a determinationthat the current location is associated with the first account, forconcurrently displaying, on the display, the visual indication of thedefault payment account and a visual indication of the first account;and wherein the default payment account and the first account are linkedto the electronic device and the default payment account and the firstaccount are different.

An electronic device, comprising: a display; a touch-sensitive surface;and means for receiving an input requesting to enable the device for apayment transaction; and means, responsive to receiving the input, for:detecting, using the location sensor, a current location; determiningwhether a set of one or more payment criteria have been met, wherein theset of one or more payment criteria includes a criterion that is metwhen the current location is associated with a first payment account; inaccordance with a determination that the set of one or more paymentcriteria is not met, displaying, on the display, a visual indication ofa default payment account, wherein the default payment account isdifferent from the first payment account; and in accordance with adetermination that the set of one or more payment criteria is met,displaying, on the display, a visual indication of the first paymentaccount.

An electronic device, comprising: a display; a touch-sensitive surface;and means for receiving an input requesting to enable the device for apayment transaction; means, responsive to receiving the input, fordisplaying, on the display, a payment indication that represents aplurality of payment accounts including a first payment account and asecond payment account; means for receiving, via the one or morewireless communication elements, a request for account informationcorresponding to a payment transaction; means, responsive to receivingthe request for account information corresponding to the paymenttransaction, for: in accordance with a determination that paymentcriteria for a first payment account have been met, transmitting, viathe one or more wireless communication elements, account information forthe first payment account without transmitting account information forthe second payment account; and in accordance with a determination thatpayment criteria for the second payment account have been met,transmitting, via the one or more wireless communication elements,account information for the second payment account without transmittingaccount information for the first payment account.

An electronic device, comprising: a display; a touch-sensitive surfaceconfigured to detect intensity of contacts; and means for receiving afirst input; means, responsive to receiving the first input, for:displaying, on the display, a first user interface, wherein the firstuser interface includes: a first visual indicator identifying a paymentcard associated with multiple payment accounts, and a second visualindicator identifying a first payment account of the multiple paymentaccounts of the payment card; means for enabling the electronic deviceto use the first payment account to engage in a payment transaction viathe one or more wireless communication elements; means for detecting afirst contact on the touch-sensitive surface; means for determiningwhether a characteristic intensity of the first contact is above anintensity threshold; and means, in accordance with a determination thatthe characteristic intensity of the first contact is above the intensitythreshold, for displaying, on the display, a second user interface,wherein the second user interface enables selection between differentpayment accounts represented by the first visual indicator.

An electronic device, comprising: a display; a touch-sensitive surface;and means for receiving a first request to link a payment accountassociated with a payment card to the first electronic device; means,responsive to receiving the first request, for initiating a process forlinking the payment account to the first electronic device; means for,after successfully linking the payment account to the first electronicdevice, concurrently displaying, on the display: an indication that thepayment account has been successfully linked to the first electronicdevice; and a selectable affordance for linking the payment account to asecond electronic device different from the first electronic device; andmeans for receiving activation of the selectable affordance; and means,responsive to receiving activation of the selectable affordance, forinitiating a process for linking the payment account to the secondelectronic device.

An electronic device, comprising: a display; a touch-sensitive surface;and means for displaying, on the display, a payment-account userinterface for a second electronic device that is associated with thefirst electronic device, wherein displaying the payment-account userinterface includes concurrently displaying: a representation of a firstpayment account along with status information for the first paymentaccount indicating that the first payment account is linked to thesecond electronic device and that the second electronic device isconfigured to enable payment using the first payment account; and arepresentation of a second payment account along with status informationfor the second payment account indicating that the second paymentaccount is linked to the first electronic device but is not linked tothe second electronic device.

A non-transitory computer-readable storage medium comprising one or moreprograms for execution by one or more processors of an electronic devicewith a display, a touch-sensitive surface, and one or more wirelesscommunication elements, the one or more programs including instructionswhich, when executed by the one or more processors, cause the electronicdevice to: receive an input requesting to enable the device for apayment transaction; in response to receiving the input requesting toenable the device for a payment transaction: display, on the display, afirst visual indicator identifying a first account; and enable theelectronic device to participate in a transaction using the firstaccount via the one or more wireless communication elements; receive oneor more swipe inputs in a first direction via the touch-sensitivesurface; in response to receiving the one or more user swipe inputs:display, on the display, a second visual indicator identifying a secondaccount; and enable the electronic device to participate in atransaction using the second account via the one or more wirelesscommunication elements; and wherein the first visual indicator isdifferent from the second visual indicator.

An electronic device comprising: a display, a touch-sensitive surface;one or more wireless communication elements one or more processors;memory; and one or more programs stored in memory, includinginstructions which, when executed by the one or more processors, causethe electronic device to: receive an input requesting to enable thedevice for a payment transaction; in response to receiving the inputrequesting to enable the device for a payment transaction: display, onthe display, a first visual indicator identifying a first account; andenable the electronic device to participate in a transaction using thefirst account via the one or more wireless communication elements;receive one or more swipe inputs in a first direction via thetouch-sensitive surface; in response to receiving the one or more userswipe inputs: display, on the display, a second visual indicatoridentifying a second account; and enable the electronic device toparticipate in a transaction using the second account via the one ormore wireless communication elements; and wherein the first visualindicator is different from the second visual indicator.

A non-transitory computer-readable storage medium comprising one or moreprograms for execution by one or more processors of an electronic devicewith a display and a location sensor, the one or more programs includinginstructions which, when executed by the one or more processors, causethe electronic device to: detect, using the location sensor, a currentlocation; determine whether the current location is associated with afirst account; in accordance with a failure to determine that thecurrent location is associated with an account other than a defaultpayment account, display, on the display, a visual indication of adefault payment account; in accordance with a determination that thecurrent location is associated with the first account, concurrentlydisplay, on the display, the visual indication of the default paymentaccount and a visual indication of the first account; and wherein thedefault payment account and the first account are linked to theelectronic device and the default payment account and the first accountare different.

An electronic device comprising: a display; a location sensor; one ormore processors; memory; and one or more programs stored in memory,including instructions which, when executed by the one or moreprocessors, cause the electronic device to: detect, using the locationsensor, a current location; determine whether the current location isassociated with a first account; in accordance with a failure todetermine that the current location is associated with an account otherthan a default payment account, display, on the display, a visualindication of a default payment account; in accordance with adetermination that the current location is associated with the firstaccount, concurrently display, on the display, the visual indication ofthe default payment account and a visual indication of the firstaccount; and wherein the default payment account and the first accountare linked to the electronic device and the default payment account andthe first account are different.

A non-transitory computer-readable storage medium comprising one or moreprograms for execution by one or more processors of an electronic devicewith a display and a location sensor, the one or more programs includinginstructions which, when executed by the one or more processors, causethe electronic device to: receive an input requesting to enable thedevice for a payment transaction; and in response to receiving theinput: detect, using the location sensor, a current location; determinewhether a set of one or more payment criteria have been met, wherein theset of one or more payment criteria includes a criterion that is metwhen the current location is associated with a first payment account; inaccordance with a determination that the set of one or more paymentcriteria is not met, display, on the display, a visual indication of adefault payment account, wherein the default payment account isdifferent from the first payment account; and in accordance with adetermination that the set of one or more payment criteria is met,display, on the display, a visual indication of the first paymentaccount.

An electronic device comprising: a display; a location sensor; one ormore processors; memory; and one or more programs stored in memory,including instructions which, when executed by the one or moreprocessors, cause the electronic device to: receive an input requestingto enable the device for a payment transaction; and in response toreceiving the input: detect, using the location sensor, a currentlocation; determine whether a set of one or more payment criteria havebeen met, wherein the set of one or more payment criteria includes acriterion that is met when the current location is associated with afirst payment account; in accordance with a determination that the setof one or more payment criteria is not met, display, on the display, avisual indication of a default payment account, wherein the defaultpayment account is different from the first payment account; and inaccordance with a determination that the set of one or more paymentcriteria is met, display, on the display, a visual indication of thefirst payment account.

A non-transitory computer-readable storage medium comprising one or moreprograms for execution by one or more processors of an electronic devicewith a display and one or more wireless communication elements, the oneor more programs including instructions which, when executed by the oneor more processors, cause the electronic device to: receive an inputrequesting to enable the device for a payment transaction; in responseto receiving the input, display, on the display, a payment indicationthat represents a plurality of payment accounts including a firstpayment account and a second payment account; receive, via the one ormore wireless communication elements, a request for account informationcorresponding to a payment transaction; in response to receiving therequest for account information corresponding to the paymenttransaction: in accordance with a determination that payment criteriafor a first payment account have been met, transmit, via the one or morewireless communication elements, account information for the firstpayment account without transmitting account information for the secondpayment account; and in accordance with a determination that paymentcriteria for the second payment account have been met, transmit, via theone or more wireless communication elements, account information for thesecond payment account without transmitting account information for thefirst payment account.

An electronic device comprising: a display; one or more wirelesscommunication elements; one or more processors; memory; and one or moreprograms stored in memory, including instructions which, when executedby the one or more processors, cause the electronic device to: receivean input requesting to enable the device for a payment transaction; inresponse to receiving the input, display, on the display, a paymentindication that represents a plurality of payment accounts including afirst payment account and a second payment account; receive, via the oneor more wireless communication elements, a request for accountinformation corresponding to a payment transaction; in response toreceiving the request for account information corresponding to thepayment transaction: in accordance with a determination that paymentcriteria for a first payment account have been met, transmit, via theone or more wireless communication elements, account information for thefirst payment account without transmitting account information for thesecond payment account; and in accordance with a determination thatpayment criteria for the second payment account have been met, transmit,via the one or more wireless communication elements, account informationfor the second payment account without transmitting account informationfor the first payment account.

A non-transitory computer-readable storage medium comprising one or moreprograms for execution by one or more processors of an electronic devicewith a display, a touch-sensitive surface configured to detect intensityof contacts, and one or more wireless communication elements, the one ormore programs including instructions which, when executed by the one ormore processors, cause the electronic device to: receive a first input;in response to receiving the first input: display, on the display, afirst user interface, wherein the first user interface includes: a firstvisual indicator identifying a payment card associated with multiplepayment accounts, and a second visual indicator identifying a firstpayment account of the multiple payment accounts of the payment card;enable the electronic device to use the first payment account to engagein a payment transaction via the one or more wireless communicationelements; detect a first contact on the touch-sensitive surface;determine whether a characteristic intensity of the first contact isabove an intensity threshold; and in accordance with a determinationthat the characteristic intensity of the first contact is above theintensity threshold, display, on the display, a second user interface,wherein the second user interface enables selection between differentpayment accounts represented by the first visual indicator.

An electronic device comprising: a display; a touch-sensitive surfaceconfigured to detect intensity of contacts; one or more wirelesscommunication elements; one or more processors; memory; and one or moreprograms stored in memory, including instructions which, when executedby the one or more processors, cause the electronic device to: receive afirst input; in response to receiving the first input: display, on thedisplay, a first user interface, wherein the first user interfaceincludes: a first visual indicator identifying a payment card associatedwith multiple payment accounts, and a second visual indicatoridentifying a first payment account of the multiple payment accounts ofthe payment card; enable the electronic device to use the first paymentaccount to engage in a payment transaction via the one or more wirelesscommunication elements; detect a first contact on the touch-sensitivesurface; determine whether a characteristic intensity of the firstcontact is above an intensity threshold; and in accordance with adetermination that the characteristic intensity of the first contact isabove the intensity threshold, display, on the display, a second userinterface, wherein the second user interface enables selection betweendifferent payment accounts represented by the first visual indicator.

A non-transitory computer-readable storage medium comprising one or moreprograms for execution by one or more processors of a first electronicdevice with a display and one or more wireless communication elements,the one or more programs including instructions which, when executed bythe one or more processors, cause the first electronic device to:receive a first request to link a payment account associated with apayment card to the first electronic device; in response to receivingthe first request, initiate a process for linking the payment account tothe first electronic device; after successfully linking the paymentaccount to the first electronic device, concurrently display, on thedisplay: an indication that the payment account has been successfullylinked to the first electronic device; and a selectable affordance forlinking the payment account to a second electronic device different fromthe first electronic device; and receive activation of the selectableaffordance; and in response to receiving activation of the selectableaffordance, initiate a process for linking the payment account to thesecond electronic device.

A first electronic device comprising: a display; one or more wirelesscommunication elements; one or more processors; memory; and one or moreprograms stored in memory, including instructions which, when executedby the one or more processors, cause the first electronic device to:receive a first request to link a payment account associated with apayment card to the first electronic device; in response to receivingthe first request, initiate a process for linking the payment account tothe first electronic device; after successfully linking the paymentaccount to the first electronic device, concurrently display, on thedisplay: an indication that the payment account has been successfullylinked to the first electronic device; and a selectable affordance forlinking the payment account to a second electronic device different fromthe first electronic device; and receive activation of the selectableaffordance; and in response to receiving activation of the selectableaffordance, initiate a process for linking the payment account to thesecond electronic device.

A non-transitory computer-readable storage medium comprising one or moreprograms for execution by one or more processors of a first electronicdevice with a display and one or more wireless communication elements,the one or more programs including instructions which, when executed bythe one or more processors, cause the first electronic device to:display, on the display, a payment-account user interface for a secondelectronic device that is associated with the first electronic device,wherein displaying the payment-account user interface includesconcurrently displaying: a representation of a first payment accountalong with status information for the first payment account indicatingthat the first payment account is linked to the second electronic deviceand that the second electronic device is configured to enable paymentusing the first payment account; and a representation of a secondpayment account along with status information for the second paymentaccount indicating that the second payment account is linked to thefirst electronic device but is not linked to the second electronicdevice.

A first electronic device comprising: a display; one or more wirelesscommunication elements; one or more processors; memory; and one or moreprograms stored in memory, including instructions which, when executedby the one or more processors, cause the first electronic device to:display, on the display, a payment-account user interface for a secondelectronic device that is associated with the first electronic device,wherein displaying the payment-account user interface includesconcurrently displaying: a representation of a first payment accountalong with status information for the first payment account indicatingthat the first payment account is linked to the second electronic deviceand that the second electronic device is configured to enable paymentusing the first payment account; and a representation of a secondpayment account along with status information for the second paymentaccount indicating that the second payment account is linked to thefirst electronic device but is not linked to the second electronicdevice.

An electronic device, comprising: a touch-sensitive surface unit; adisplay unit; a wireless communication unit including one or morewireless communication elements; and a processing unit coupled to thedisplay unit, the touch-sensitive surface unit, and the wirelesscommunication unit, the processing unit configured to: receive an inputrequesting to enable the device for a payment transaction; in responseto receiving the input requesting to enable the device for a paymenttransaction: enable display, on the display unit, of a first visualindicator identifying a first account; and enable the electronic deviceto participate in a transaction using the first account via the one ormore wireless communication elements; receive one or more swipe inputsin a first direction via the touch-sensitive surface unit; in responseto receiving the one or more user swipe inputs: enable display, on thedisplay unit, of a second visual indicator identifying a second account;and enable the electronic device to participate in a transaction usingthe second account via the one or more wireless communication elements;and wherein the first visual indicator is different from the secondvisual indicator.

An electronic device, comprising: a display unit; a location sensorunit; and a processing unit coupled to the display unit and the locationsensor unit, the processing unit configured to: detect, using thelocation sensor unit, a current location; determine whether the currentlocation is associated with a first account; in accordance with afailure to determine that the current location is associated with anaccount other than a default payment account, enable display, on thedisplay unit, of a visual indication of a default payment account; inaccordance with a determination that the current location is associatedwith the first account, enable concurrent display, on the display unit,of the visual indication of the default payment account and a visualindication of the first account; and wherein the default payment accountand the first account are linked to the electronic device and thedefault payment account and the first account are different.

An electronic device, comprising: a display unit; a location sensorunit; and a processing unit coupled to the display unit and the locationsensor unit, the processing unit configured to: receive an inputrequesting to enable the device for a payment transaction; and inresponse to receiving the input: detect, using the location sensor unit,a current location; determine whether a set of one or more paymentcriteria have been met, wherein the set of one or more payment criteriaincludes a criterion that is met when the current location is associatedwith a first payment account; in accordance with a determination thatthe set of one or more payment criteria is not met, enable display, onthe display unit, of a visual indication of a default payment account,wherein the default payment account is different from the first paymentaccount; and in accordance with a determination that the set of one ormore payment criteria is met, enable display, on the display unit, of avisual indication of the first payment account.

An electronic device, comprising: a display unit; a wirelesscommunication unit including one or more wireless communicationelements; and a processing unit coupled to the display unit and thewireless communication unit, the processing unit configured to: receivean input requesting to enable the device for a payment transaction; inresponse to receiving the input, enable display, on the display unit, ofa payment indication that represents a plurality of payment accountsincluding a first payment account and a second payment account; receive,via the one or more wireless communication elements, a request foraccount information corresponding to a payment transaction; in responseto receiving the request for account information corresponding to thepayment transaction: in accordance with a determination that paymentcriteria for a first payment account have been met, transmit, via theone or more wireless communication elements, account information for thefirst payment account without transmitting account information for thesecond payment account; and in accordance with a determination thatpayment criteria for the second payment account have been met, transmit,via the one or more wireless communication elements, account informationfor the second payment account without transmitting account informationfor the first payment account.

An electronic device, comprising: a display unit; a touch-sensitivesurface unit; a wireless communication unit including one or morewireless communication elements; and a processing unit coupled to thedisplay unit, the touch-sensitive surface unit configured to detectintensity of contacts, and the wireless communication unit, theprocessing unit configured to: receive a first input; in response toreceiving the first input: enable display, on the display unit, of afirst user interface, wherein the first user interface includes: a firstvisual indicator identifying a payment card associated with multiplepayment accounts, and a second visual indicator identifying a firstpayment account of the multiple payment accounts of the payment card;enable the electronic device to use the first payment account to engagein a payment transaction via the one or more wireless communicationelements; detect a first contact on the touch-sensitive surface unit;determine whether a characteristic intensity of the first contact isabove an intensity threshold; and in accordance with a determinationthat the characteristic intensity of the first contact is above theintensity threshold, enable display, on the display unit, of a seconduser interface, wherein the second user interface enables selectionbetween different payment accounts represented by the first visualindicator.

A first electronic device, comprising: a display unit; a wirelesscommunications unit with one or more wireless communication elements;and a processing unit coupled to the display unit and the wirelesscommunications unit, the processing unit configured to: receive a firstrequest to link a payment account associated with a payment card to thefirst electronic device; in response to receiving the first request,initiate a process for linking the payment account to the firstelectronic device; after successfully linking the payment account to thefirst electronic device, enable concurrent display, on the display unit,of: an indication that the payment account has been successfully linkedto the first electronic device; and a selectable affordance for linkingthe payment account to a second electronic device different from thefirst electronic device; and receive activation of the selectableaffordance; and in response to receiving activation of the selectableaffordance, initiate a process for linking the payment account to thesecond electronic device.

A first electronic device, comprising: a display unit; a wirelesscommunication unit that includes one or more wireless communicationelements; and a processing unit coupled to the display unit and thewireless communication unit, the processing unit configured to: enabledisplay, on the display unit, of a payment-account user interface for asecond electronic device that is associated with the first electronicdevice, wherein enabling display of the payment-account user interfaceincludes enabling concurrent display of: a representation of a firstpayment account along with status information for the first paymentaccount indicating that the first payment account is linked to thesecond electronic device and that the second electronic device isconfigured to enable payment using the first payment account; and arepresentation of a second payment account along with status informationfor the second payment account indicating that the second paymentaccount is linked to the first electronic device but is not linked tothe second electronic device.

A transitory computer-readable storage medium comprising one or moreprograms for execution by one or more processors of an electronic devicewith a display, a touch-sensitive surface, and one or more wirelesscommunication elements, the one or more programs including instructionswhich, when executed by the one or more processors, cause the electronicdevice to: receive an input requesting to enable the device for apayment transaction; in response to receiving the input requesting toenable the device for a payment transaction: display, on the display, afirst visual indicator identifying a first account; and enable theelectronic device to participate in a transaction using the firstaccount via the one or more wireless communication elements; receive oneor more swipe inputs in a first direction via the touch-sensitivesurface; in response to receiving the one or more user swipe inputs:display, on the display, a second visual indicator identifying a secondaccount; and enable the electronic device to participate in atransaction using the second account via the one or more wirelesscommunication elements; and wherein the first visual indicator isdifferent from the second visual indicator.

A transitory computer-readable storage medium comprising one or moreprograms for execution by one or more processors of an electronic devicewith a display and a location sensor, the one or more programs includinginstructions which, when executed by the one or more processors, causethe electronic device to: detect, using the location sensor, a currentlocation; determine whether the current location is associated with afirst account; in accordance with a failure to determine that thecurrent location is associated with an account other than a defaultpayment account, display, on the display, a visual indication of adefault payment account; in accordance with a determination that thecurrent location is associated with the first account, concurrentlydisplay, on the display, the visual indication of the default paymentaccount and a visual indication of the first account; and wherein thedefault payment account and the first account are linked to theelectronic device and the default payment account and the first accountare different.

A transitory computer-readable storage medium comprising one or moreprograms for execution by one or more processors of an electronic devicewith a display and a location sensor, the one or more programs includinginstructions which, when executed by the one or more processors, causethe electronic device to: receive an input requesting to enable thedevice for a payment transaction; and in response to receiving theinput: detect, using the location sensor, a current location; determinewhether a set of one or more payment criteria have been met, wherein theset of one or more payment criteria includes a criterion that is metwhen the current location is associated with a first payment account; inaccordance with a determination that the set of one or more paymentcriteria is not met, display, on the display, a visual indication of adefault payment account, wherein the default payment account isdifferent from the first payment account; and in accordance with adetermination that the set of one or more payment criteria is met,display, on the display, a visual indication of the first paymentaccount.

A transitory computer-readable storage medium comprising one or moreprograms for execution by one or more processors of an electronic devicewith a display and one or more wireless communication elements, the oneor more programs including instructions which, when executed by the oneor more processors, cause the electronic device to: receive an inputrequesting to enable the device for a payment transaction; in responseto receiving the input, display, on the display, a payment indicationthat represents a plurality of payment accounts including a firstpayment account and a second payment account; receive, via the one ormore wireless communication elements, a request for account informationcorresponding to a payment transaction; in response to receiving therequest for account information corresponding to the paymenttransaction: in accordance with a determination that payment criteriafor a first payment account have been met, transmit, via the one or morewireless communication elements, account information for the firstpayment account without transmitting account information for the secondpayment account; and in accordance with a determination that paymentcriteria for the second payment account have been met, transmit, via theone or more wireless communication elements, account information for thesecond payment account without transmitting account information for thefirst payment account.

A transitory computer-readable storage medium comprising one or moreprograms for execution by one or more processors of an electronic devicewith a display, a touch-sensitive surface configured to detect intensityof contacts, and one or more wireless communication elements, the one ormore programs including instructions which, when executed by the one ormore processors, cause the electronic device to: receive a first input;in response to receiving the first input: display, on the display, afirst user interface, wherein the first user interface includes: a firstvisual indicator identifying a payment card associated with multiplepayment accounts, and a second visual indicator identifying a firstpayment account of the multiple payment accounts of the payment card;enable the electronic device to use the first payment account to engagein a payment transaction via the one or more wireless communicationelements; detect a first contact on the touch-sensitive surface;determine whether a characteristic intensity of the first contact isabove an intensity threshold; and in accordance with a determinationthat the characteristic intensity of the first contact is above theintensity threshold, display, on the display, a second user interface,wherein the second user interface enables selection between differentpayment accounts represented by the first visual indicator.

A transitory computer-readable storage medium comprising one or moreprograms for execution by one or more processors of a first electronicdevice with a display and one or more wireless communication elements,the one or more programs including instructions which, when executed bythe one or more processors, cause the first electronic device to:receive a first request to link a payment account associated with apayment card to the first electronic device; in response to receivingthe first request, initiate a process for linking the payment account tothe first electronic device; after successfully linking the paymentaccount to the first electronic device, concurrently display, on thedisplay: an indication that the payment account has been successfullylinked to the first electronic device; and a selectable affordance forlinking the payment account to a second electronic device different fromthe first electronic device; and receive activation of the selectableaffordance; and in response to receiving activation of the selectableaffordance, initiate a process for linking the payment account to thesecond electronic device.

A transitory computer-readable storage medium comprising one or moreprograms for execution by one or more processors of a first electronicdevice with a display and one or more wireless communication elements,the one or more programs including instructions which, when executed bythe one or more processors, cause the first electronic device to:display, on the display, a payment-account user interface for a secondelectronic device that is associated with the first electronic device,wherein displaying the payment-account user interface includesconcurrently displaying: a representation of a first payment accountalong with status information for the first payment account indicatingthat the first payment account is linked to the second electronic deviceand that the second electronic device is configured to enable paymentusing the first payment account; and a representation of a secondpayment account along with status information for the second paymentaccount indicating that the second payment account is linked to thefirst electronic device but is not linked to the second electronicdevice.

Thus, devices are provided with faster, more efficient methods andinterfaces for linking accounts to the device, selecting an account foruse in a transaction, and transmitting account information in atransaction, thereby increasing the effectiveness, efficiency, and usersatisfaction with such devices. Such methods and interfaces maycomplement or replace other methods for performing similar tasks.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIG. 5I illustrates exemplary devices connected via one or morecommunication channels to complete a payment transaction in accordancewith some embodiments.

FIGS. 6A-6G illustrate exemplary techniques and exemplary userinterfaces for receiving a selection of an account, in accordance withsome embodiments.

FIG. 7 is a flow diagram illustrating a method for receiving a selectionof an account, in accordance with some embodiments.

FIGS. 8A-8D illustrate exemplary techniques and exemplary userinterfaces for selecting an account, in accordance with someembodiments.

FIG. 9 is a flow diagram illustrating a method for selecting an account,in accordance with some embodiments.

FIGS. 10A-10E illustrate exemplary techniques and exemplary userinterfaces for selecting an account, in accordance with someembodiments.

FIG. 11 is a flow diagram illustrating a method for selecting anaccount, in accordance with some embodiments.

FIGS. 12A-12D illustrate exemplary techniques and exemplary userinterfaces for transmitting account information of an account, inaccordance with some embodiments.

FIG. 13 is a flow diagram illustrating a method for transmitting accountinformation of an account, in accordance with some embodiments.

FIGS. 14A-14E illustrate exemplary techniques and exemplary userinterfaces for receiving a selection of an account, in accordance withsome embodiments.

FIG. 15 is a flow diagram illustrating a method for receiving aselection of an account, in accordance with some embodiments.

FIGS. 16A-16G illustrate exemplary techniques and exemplary userinterfaces for linking a payment account to one or more electronicdevices, in accordance with some embodiments.

FIG. 17 is a flow diagram illustrating a method for linking a paymentaccount to one or more electronic devices, in accordance with someembodiments.

FIGS. 18A-18C illustrate exemplary techniques and exemplary userinterfaces for linking a payment account to an electronic device, inaccordance with some embodiments.

FIG. 19 is a flow diagram illustrating a method for linking a paymentaccount to an electronic device, in accordance with some embodiments.

FIGS. 20-26 illustrate functional block diagrams in accordance with someembodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for linking accounts to the electronic device, selectingan account for use in a transaction, and transmitting accountinformation in a transaction. In particular, there is a need to provideefficient methods and interfaces for wearable devices, such as smartwatches. Such techniques can reduce the cognitive burden on a user whoaccess event notifications, thereby enhancing productivity. Further,such techniques can reduce processor and battery power otherwise wastedon redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices. FIGS. 6A-6G illustrate exemplary techniques andexemplary user interfaces for receiving a selection of an account. FIG.7 is a flow diagram illustrating a method for receiving a selection ofan account. The user interfaces in FIGS. 6A-6G are used to illustratethe processes in FIG. 7 . FIGS. 8A-8D illustrate exemplary techniquesand exemplary user interfaces for selecting an account. FIG. 9 is a flowdiagram illustrating a method for selecting an account. The userinterfaces in FIGS. 8A-8D are used to illustrate the processes in FIG. 9. FIGS. 10A-10E illustrate exemplary techniques and exemplary userinterfaces for selecting an account. FIG. 11 is a flow diagramillustrating a method for selecting an account, in accordance with someembodiments. The user interfaces in FIGS. 10A-10E are used to illustratethe processes in FIG. 11 . FIGS. 12A-12D illustrate exemplary techniquesand exemplary user interfaces for transmitting account information of anaccount. FIG. 13 is a flow diagram illustrating a method fortransmitting account information of an account, in accordance with someembodiments. The user interfaces in FIGS. 12A-12D are used to illustratethe processes in FIG. 13 . FIGS. 14A-14E illustrate exemplary techniquesand exemplary user interfaces for receiving a selection of an account.FIG. 15 is a flow diagram illustrating a method for receiving aselection of an account. The user interfaces in FIGS. 14A-14E are usedto illustrate the processes in FIG. 15 . FIGS. 16A-16G illustrateexemplary techniques and exemplary user interfaces for linking a paymentaccount to one or more electronic devices. FIG. 17 is a flow diagramillustrating a method for linking a payment account to one or moreelectronic devices. The user interfaces in FIGS. 16A-16G are used toillustrate the processes in FIG. 17 . FIGS. 18A-18C illustrate exemplarytechniques and exemplary user interfaces for linking a payment accountto an electronic device, in accordance with some embodiments. FIG. 19 isa flow diagram illustrating a method for linking a payment account to anelectronic device. The user interfaces in FIGS. 18A-18C are used toillustrate the processes in FIG. 19 .

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, California. Other portableelectronic devices, such as laptops or tablet computers withtouch-sensitive surfaces (e.g., touch screen displays and/or touchpads),are, optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 may include one or more computer-readable storage mediums.The computer-readable storage mediums may be tangible andnon-transitory. Memory 102 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 122 may control access tomemory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2 ). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2 ) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2 ).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, California.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 )stores device/global internal state 157, as shown in FIGS. 1A and 3 .Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., DARWIN, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 may be used to manage an address book orcontact list (e.g., stored in application internal state 192 of contactsmodule 137 in memory 102 or memory 370), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 137, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation, and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions, data on stores and otherpoints of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 152, FIG. 1A). In some embodiments, memory 102may store a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules may be combined or otherwise rearranged invarious embodiments. In some embodiments, memory 370 may store a subsetof the modules and data structures identified above. Furthermore, memory370 may store additional modules and data structures not describedabove.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 may optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface) may haveone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data thatrepresents the intensity of touches. The user interface of device 500can respond to touches based on their intensity, meaning that touches ofdifferent intensities can invoke different user interface operations ondevice 500.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 may be a rotatable input device or a depressible androtatable input device, for example. Input mechanism 508 may be abutton, in some examples.

Input mechanism 508 may be a microphone, in some examples. Personalelectronic device 500 can include various sensors, such as GPS sensor532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, and/or a combination thereof, all ofwhich can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 700, 900, 1100, 1300,1500, 1700, and 1900 (FIGS. 7, 9, 11, 13, 15, 17, and 19 ). Thecomputer-executable instructions can also be stored and/or transportedwithin any non-transitory computer-readable storage medium for use by orin connection with an instruction execution system, apparatus, ordevice, such as a computer-based system, processor-containing system, orother system that can fetch the instructions from the instructionexecution system, apparatus, or device and execute the instructions. Forpurposes of this document, a “non-transitory computer-readable storagemedium” can be any medium that can tangibly contain or storecomputer-executable instructions for use by or in connection with theinstruction execution system, apparatus, or device. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 5B, but caninclude other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5 ). Forexample, an image (e.g., icon), a button, and text (e.g., hyperlink) mayeach constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of: an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms eliminatenarrow spikes or dips in the intensities of the swipe contact forpurposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

FIG. 5I illustrates exemplary devices connected via one or morecommunication channels to complete a payment transaction in accordancewith some embodiments. One or more exemplary electronic devices (e.g.,devices 100, 300, and 500) are configured to optionally detect input(e.g., a particular user input, an NFC field) and optionally transmitpayment information (e.g., using NFC). The one or more electronicdevices optionally include NFC hardware and are configured to beNFC-enabled.

The electronic devices (e.g., devices 100, 300, and 500) are optionallyconfigured to store payment account information associated with each ofone or more payment accounts. Payment account information includes, forexample, one or more of: a person's or company's name, a billingaddress, a login, a password, an account number, an expiration date, asecurity code, a telephone number, a bank associated with the paymentaccount (e.g., an issuing bank), and a card network identifier. In someexamples, payment account information includes include an image, such asa picture of a payment card (e.g., taken by the device and/or receivedat the device). In some examples, the electronic devices receive userinput including at least some payment account information (e.g.,receiving user-entered credit, debit, account, or gift card number andexpiration date). In some examples, the electronic devices detect atleast some payment account information from an image (e.g., of a paymentcard captured by a camera sensor of the device). In some examples, theelectronic devices receive at least some payment account informationfrom another device (e.g., another user device or a server). In someexamples, the electronic device receives payment account informationfrom a server associated with another service for which an account for auser or user device previously made a purchase or identified paymentaccount data (e.g., an app for renting or selling audio and/or videofiles).

In some embodiments, a payment account is added to an electronic device(e.g., device 100, 300, and 500), such that payment account informationis securely stored on the electronic device. In some examples, after auser initiates such process, the electronic device transmits informationfor the payment account to a transaction-coordination server, which thencommunicates with a server operated by a payment network for the account(e.g., a payment server) to ensure a validity of the information. Theelectronic device is optionally configured to receive a script from theserver that allows the electronic device to program payment informationfor the account onto the secure element.

In some embodiments, communication among electronic devices 100, 300,and 500 facilitates transactions (e.g., generally or specifictransactions). For example, a first electronic device (e.g., 100) canserve as a provisioning or managing device, and can send notificationsof new or updated payment account data (e.g., information for a newaccount, updated information for an existing account, and/or an alertpertaining to an existing account) to a second electronic device (e.g.,500). In another example, a first electronic device (e.g., 100) can senddata to a second election device, wherein the data reflects informationabout payment transactions facilitated at the first electronic device.The information optionally includes one or more of: a payment amount, anaccount used, a time of purchase, and whether a default account waschanged. The second device (e.g., 500) optionally uses such informationto update a default payment account (e.g., based on a learning algorithmor explicit user input).

Electronic devices (e.g., 100, 300, 500) are configured to communicatewith each over any of a variety of networks. For example, the devicescommunicate using a Bluetooth connection 580 (e.g., which includes atraditional Bluetooth connection or a Bluetooth Low Energy connection)or using a WiFi network 582. Communications among user devices are,optionally, conditioned to reduce the possibility of inappropriatelysharing information across devices. For example, communications relatingto payment information requires that the communicating devices be paired(e.g., be associated with each other via an explicit user interaction)or be associated with a same user account.

In some embodiments, an electronic device (e.g., 100, 300, 500) is usedto communicate with a point-of-sale (POS) payment terminal 820, 1220,which is optionally NFC-enabled. The communication optionally occursusing a variety of communication channels and/or technologies. In oneexamples, electronic device (e.g., 100, 300, 500) communicates withpayment terminal 820, 1220 using an NFC channel 584. In some examples,payment terminal 820, 1220 communicates with an electronic device (e.g.,100, 300, 500) using a peer-to-peer NFC mode. Electronic device (e.g.,100, 300, 500) is optionally configured transmit a signal to paymentterminal 820, 1220 that includes payment information for a paymentaccount (e.g., a default account or an account selected for theparticular transaction).

In some embodiments, generation of and/or transmission of the signal iscontrolled by a secure element in the electronic device (e.g., 100, 300,500). The secure element optionally requires a particular user inputprior to releasing payment information. For example, the secure elementoptionally requires detection that the electronic device is being worn,detection of a button press, detection of entry of a passcode, detectionof a touch, detection of one or more option selections (e.g., receivedwhile interacting with an application), detection of a fingerprintsignature, detection of a voice or voice command, and or detection of agesture or movement (e.g., rotation or acceleration). In some examples,if a communication channel (e.g., an NFC communication channel) withanother device (e.g., payment terminal 820, 1220) is established withina defined time period from detection of the input, the secure elementreleases payment information to be transmitted to the other device(e.g., payment terminal 820, 1220). In some examples, the secure elementis a hardware component that controls release of secure information. Insome examples, the secure element is a software component that controlsrelease of secure information.

In some embodiments, protocols related to transaction participationdepend on, for example, device types. For example, a condition forgenerating and/or transmitting payment information can be different fora wearable device (e.g., device 500) and a phone (e.g., device 100). Forexample, a generation and/or transmission condition for a wearabledevice includes detecting that a button has been pressed (e.g., after asecurity verification), while a corresponding condition for a phone doesnot require button-depression and instead requires detection ofparticular interaction with an application. In some examples, acondition for transmitting and/or releasing payment information includesreceiving particular input on each of multiple devices. For example,release of payment information optionally requires detection of afingerprint and/or passcode at the device (e.g., device 100) anddetection of a mechanical input (e.g., button press) on another device(e.g., device 500).

Payment terminal 820, 1220 optionally uses the payment information togenerate a signal to transmit to a payment server 590 to determinewhether the payment is authorized. Payment server 590 optionallyincludes any device or system configured to receive payment informationassociated with a payment account and to determine whether a proposedpurchase is authorized. In some examples, payment server 590 includes aserver of an issuing bank.

Payment terminal 820, 1220 communicates with payment server 590 directlyor indirectly via one or more other devices or systems (e.g., a serverof an acquiring bank and/or a server of a card network).

Payment server 590 optionally uses at least some of the paymentinformation to identify a user account from among a database of useraccounts (e.g., 592). For example, each user account includes paymentinformation. An account is, optionally, located by locating an accountwith particular payment information matching that from the POScommunication. In some examples, a payment is denied when providedpayment information is not consistent (e.g., an expiration date does notcorrespond to a credit, debit or gift card number) or when no accountincludes payment information matching that from the POS communication.

In some embodiments, data for the user account further identifies one ormore restrictions (e.g., credit limits); current or previous balances;previous transaction dates, locations and/or amounts; account status(e.g., active or frozen), and/or authorization instructions. In someexamples, the payment server (e.g., 590) uses such data to determinewhether to authorize a payment. For example, a payment server denies apayment when a purchase amount added to a current balance would resultin exceeding an account limit, when an account is frozen, when aprevious transaction amount exceeds a threshold, or when a previoustransaction count or frequency exceeds a threshold.

In some embodiments, payment server 590 responds to POS payment terminal820, 1220 with an indication as to whether a proposed purchase isauthorized or denied. In some examples, POS payment terminal 820, 1220transmits a signal to the electronic device (e.g., 100, 300, 500) toidentify the result. For example, POS payment terminal 820, 1220 sends areceipt to the electronic device (e.g., 100, 300, 500) when a purchaseis authorized (e.g., via a transaction-coordination server that managesa transaction app on the user device). In some instances, POS paymentterminal 820, 1220 presents an output (e.g., a visual or audio output)indicative of the result. Payment can be sent to a merchant as part ofthe authorization process or can be subsequently sent.

In some embodiments, the electronic device (e.g., 100, 300, 500)participates in a transaction that is completed without involvement ofPOS payment terminal 820, 1220. For example, upon detecting that amechanical input has been received, a secure element in the electronicdevice (e.g., 100, 300, 500) releases payment information to allow anapplication on the electronic device to access the information (e.g.,and to transmit the information to a server associated with theapplication).

Attention is now directed towards embodiments of user interfaces (“UP”)and associated processes that may be implemented on an electronicdevice, such as portable multifunction device 100, device 300, or device500.

Some embodiments described below relate to loyalty accounts. Forexample, a loyalty account may be an account of a loyalty program thatprovides a structured marketing effort that rewards customers/members. Aloyalty account is optionally specific to one particular company, store,or chain of stores. A company (such as a retail store or chain ofstores) may use a loyalty account to track purchases or otherinformation about a user (e.g., a purchaser). The loyalty accounttypically entitles the user to a discount on a current or futurepurchase and/or an allotment of points that may be used toward futurepurchases or gifts. In some examples, loyalty accounts cannot be usedfor making payments. Generally, loyalty accounts cannot be used make amonetary payment.

Some embodiments described below relate to private label accounts. Forexample, private label accounts include payment accounts branded for aspecific merchant, independent dealer, or manufacturer. Some privatelabel cards and private label accounts are accepted only at particularmerchants or may provide certain benefits only available at particularmerchants. For example, a particular merchant may offer a private labelaccount to customers that can only be used when making purchases throughthat particular merchant. Merchants frequently prefer to offer privatelabel accounts because it provides customers another way to shop withthe merchant, thus increasing sales and providing customers with aconvenient payment option.

Some embodiments described below relate to transmitting payment accountinformation from the electronic device to a contactless payment terminalthat enables the contactless payment terminal to engage in a paymenttransaction by, for example, routing information to one or morefinancial institutions to verify payment credentials and/or receiveauthorization to complete the transaction. An exemplary payment networkarchitecture and additional details regarding routing for paymenttransactions can be found at, for example, FIG. 2 and the accompanyingdescription of U.S. Patent Application Ser. No. 62/004,338, entitled“USER DEVICE SECURE PARTICIPATION IN TRANSACTIONS VIA LOCAL SECUREELEMENT DETECTION OF MECHANICAL INPUT”, filed May 29, 2014, (ReferenceNo. P22931USP1).

FIGS. 6A-6G illustrate exemplary techniques and exemplary userinterfaces for receiving a selection of an account, such as a loyaltyaccount or a payment account, from among multiple accounts in anelectronic wallet, in accordance with some embodiments. For example,account information of a selected account may subsequently betransmitted to an NFC-enabled payment terminal for use in a transaction(e.g., when the device is placed into a field of the payment terminal).The user interfaces in these figures are used to illustrate theprocesses described below, including the processes in FIG. 7 .

FIG. 6A illustrates wearable electronic device 500, which is, forexample, a smart watch. The device includes a display, a touch-sensitivesurface, and one or more wireless communication elements (e.g., one ormore wireless antennas such as NFC antennas, WiFi antennas). The devicereceives an input (e.g., a user input) requesting to enable the devicefor a payment transaction (e.g., the user performs a double-click ofhardware button 508 of the device which arms the device for making NFCpayments and/or for accessing an electronic wallet of the device).

In response to receiving the input requesting to enable the device for apayment transaction, and as illustrated in FIG. 6A, the device displays,on the display, a first visual indicator 602 identifying a first accountand the device enables the electronic device to participate in atransaction using the first account via the one or more wirelesscommunication elements (e.g., arming the device for making an NFCpayment using the default payment account or arming the device forperforming an NFC transaction using a loyalty account). Ready indication604 is a visual indication that the device is enabled to participate ina transaction using the first account, represented by the first visualindicator 602. First visual indicator 602 may take up less than 70% (orless than 60%, 50%, or 40%) of the total display space of the display.The device may also display, on the display, an indication 606 thatother accounts are also available or an indication 606 of the number ofother accounts available. In this example, the indication 606 includesfour paging dots. The first paging dot is of a first color that isdifferent from a second color of the second, third, and fourth pagingdots. The four paging dots indicate that a total of four accounts areavailable. The first paging dot being a different color from the otherpaging dots indicates that the device is currently displayinginformation (e.g., first visual indicator 602) corresponding to thefirst account.

At FIG. 6B, the electronic device receives one or more swipe inputs in afirst direction (e.g., one or more left swipes or one or more rightswipes) via the touch-sensitive surface. At FIG. 6B, one or more swipeinputs are detected and the first visual indicator 602 is beingtransitioned to not being displayed (e.g., by sliding the first visualindicator 602 in the first direction). In some examples, readyindication 604 is no longer displayed while the first visual indicator602 is transitioning to not being displayed.

As illustrated in FIG. 6C, in response to receiving the one or more userswipe inputs, the device displays, on the display, a second visualindicator 620 identifying a second account that is different from thefirst account and the device enables the electronic device toparticipate in a transaction using the second account via the one ormore wireless communication elements (e.g., arming the device for makingan NFC transaction using the second account and disabling the devicefrom participating in transactions using the first account). In someembodiments, second visual indicator 620 is larger than first visualindicator 602. For example, the second visual indicator takes up morethan 70% (or more than 60%, 50%, or 40%) of the total display space ofthe display. At FIG. 6C, the first visual indicator 602 is no longerdisplayed and the paging dots 606 have been updated to reflect that thedevice is currently displaying information (e.g., second visualindicator 620) corresponding to the second account. Ready indication 622is a visual indication that the device is enabled to participate in atransaction using the second account.

The first visual indicator 602 is different from the second visualindicator 610. For example, the first visual indicator 602 includes: thename of a first financial institution “AA BANK,” has a first backgroundart that corresponds to the background art of a payment card associatedwith the first account, at least a portion of an account numberassociated with the first account, and an expiration date associatedwith the first account. The second visual indicator 620 includes thename of a merchant “SUPERMARKET INC.” associated with a loyalty account,has a second background art that is different from the first backgroundart, and may or may not include at least a portion of an account numberassociated with the second account. In this example, the second visualindicator does not display an expiration date associated with the secondaccount.

In accordance with some embodiments, as illustrated in FIGS. 6A-6C, thefirst account is a payment account and the second account is a loyaltyaccount. In accordance with some embodiments, as illustrated in FIGS. 6Aand 6G, the first account is a payment account and the second account isa payment account.

In accordance with some embodiments, as illustrated in FIGS. 6D-6F,while displaying the second visual indicator (e.g., of a loyaltyaccount): the electronic device receives a card code display input(e.g., a user swipe input in a second direction different from the firstdirection; a tap on a “show barcode” affordance 626), and in response toreceiving the card code display input, the electronic device displays,on the display, visual loyalty card code information (e.g., 624; abarcode or QR code). The visual loyalty card code information mayoptionally represent account information of the second account. Forexample, at FIG. 6D, the device receives an upward swipe input on thetouch-sensitive surface, and in response displays bar code 624. The usermay have bar code 624 visually scanned by a payment terminal. Foranother example, at FIG. 6D, the device receives the same upward swipeinput on the touch-sensitive surface, and in response displaysaffordance 626, which when activated displays the visual loyalty cardcode information (e.g., 624) associated with the second account.

In accordance with some embodiments and with reference to the userinterface of FIG. 6C, the user may place the device into a field of acontactless payment terminal. While displaying the second visualindicator: the electronic device receives a request for accountinformation from a contactless payment terminal, and in response toreceiving the request for account information, transmitting, via the oneor more wireless communication elements, account information for thesecond account to the contactless payment terminal, wherein the accountinformation enables the contactless payment terminal to engage in thepayment transaction.

In accordance with some embodiments, engaging in the payment transactionincludes routing loyalty information to one or servers forconfirmation/authorization of the loyalty account (e.g., when the secondaccount is a loyalty account). In some embodiments, engaging in thepayment transaction includes routing information to one or morefinancial institutions to verify payment credentials and/or receiveauthorization to complete the transaction (e.g., when the second accountis a payment account). For example, the account information istransmitted to the contactless payment terminal using NFC.

In accordance with some embodiments (e.g., wherein the second account isa payment account), while displaying the second visual indicator andafter transmitting account information for the second account to thecontactless payment terminal: the electronic device receives, via theone or more wireless communication elements, a failure communicationfrom the contactless payment terminal (e.g., payment was rejectedbecause the payment account type is not accepted by the contactlesspayment terminal). In response to receiving the failure communication:the electronic device displays, on the display, an indication that thesecond account was not accepted and provides an option to enable theelectronic device to participate in the transaction using an accountdifferent from the second account (e.g., a default payment account thatis not a private label payment account).

In accordance with some embodiments, subsequent to (or in response to)transmitting account information for the second account to thecontactless payment terminal, the electronic device concurrentlydisplays, on the display an indication that the first account and thesecond account were both used during the payment transaction (e.g.,concurrently displaying at least a portion of the first visual indicatorand at least a portion of the second visual indicator). For example, theuser may use the electronic device to provide loyalty accountinformation using the second account and to provide payment accountinformation using the first account. As a result, both visual indicatorswill be simultaneously displayed after the transactions.

In accordance with some embodiments, enabling the electronic device toparticipate in the transaction using the second account via the one ormore wireless communication elements does not require receiving a seconduser input requesting to enable the device for a payment transaction.For example, the user does not need to double-click the hardware button508 again to arm the device to make an NFC payment or an NFC loyaltytransaction using the second account.

In accordance with some embodiments, enabling the electronic device toparticipate in the transaction using the first account includesdisplaying a first animation of a ready indicator (e.g., 604) appearingfrom under an image of a card of the first account (e.g., the firstvisual indicator 602). The ready indicator (e.g., 604) indicates thatthe device is enabled to participate in payment transactions using thefirst account. In response to receiving a portion of the one or moreuser swipe inputs, the electronic device displays a second animation ofthe ready indicator to slide the ready indicator (e.g., 604) back underthe image of the card of the first account.

In accordance with some embodiments, the electronic device displays thefirst visual indicator (e.g., 602) identifying the first account priorto enabling the electronic device to participate in the transactionusing the first account via the one or more wireless communicationelements. The electronic device displays, on the display, the secondvisual indicator (e.g., 620) identifying the second account prior toenabling the electronic device to participate in the transaction usingthe second account via the one or more wireless communication elements.

In accordance with some embodiments, one of the first account and thesecond account is a payment account and one of the first account and thesecond account is a loyalty account (e.g., the first account is apayment account and the second account is a loyalty account). The firstvisual indicator (e.g., 602) of the first account has a first dimensioncharacteristic (e.g., size or aspect ratio) and the second visualindicator (e.g., 620) of the second account has a second dimensioncharacteristic different from the first dimension characteristic (e.g.,a different size or different aspect ratio). Thus, visual indications ofloyalty accounts look different than visual indications of paymentaccounts. This helps a user quickly identify whether a loyalty accountor a payment account is displayed and/or enabled.

In accordance with some embodiments, an electronic wallet of theelectronic device includes payment account information for a pluralityof payment accounts (e.g., including the payment accounts associatedwith 602 and 610) associated with a user of the electronic device.

As illustrated in FIG. 6F, the electronic device receives a second oneor more swipe inputs in the first direction via the touch-sensitivesurface. In response, to receiving the second one or more user swipeinputs, the electronic device displays, on the display, a third visualindicator identifying a third account, and the electronic device enablesthe electronic device to participate in a transaction using the thirdaccount via the one or more wireless communication elements; and (e.g.,arming the device for making an NFC transaction using the third accountand disabling the device from participating in transactions using thesecond account). The third visual indicator is different from the firstvisual indicator and the second visual indicator.

FIG. 7 is a flow diagram illustrating a method for receiving a selectionof an account, such as a loyalty account or a payment account, fromamong multiple accounts in an electronic wallet using an electronicdevice in accordance with some embodiments. Method 700 is performed at adevice (e.g., 100, 300, 500) with a display, a touch-sensitive surface,and one or more wireless communication elements. Some operations inmethod 700 may be combined, the order of some operations may be changed,and some operations may be omitted.

As described below, method 700 provides an intuitive way for receiving aselection of an account, such as a loyalty account or a payment account,from among multiple accounts in an electronic wallet. The method reducesthe cognitive burden on a user for receiving a selection of an account,thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to select an accountfaster and more efficiently conserves power and increases the timebetween battery charges.

At block 702, the electronic device receives an input (e.g., a userinput at 508) requesting to enable the device for a payment transaction.

At block 704, in response to receiving the input requesting to enablethe device for a payment transaction, the process proceeds to blocks706-708.

At block 706, the electronic device displays, on the display, a firstvisual indicator (e.g., 602) identifying a first account. At block 708,the electronic device enables the electronic device to participate in atransaction using the first account via the one or more wirelesscommunication elements.

At block 710, the electronic device receives one or more swipe inputs ina first direction (e.g., one or more left swipes) via thetouch-sensitive surface.

At block 712, in response to receiving the one or more user swipeinputs, the process proceeds to blocks 714-716.

At block 714, the electronic device displays, on the display, a secondvisual indicator (e.g., 620) identifying a second account. At block 716,the electronic device enables the electronic device to participate in atransaction using the second account via the one or more wirelesscommunication elements, wherein the first visual indicator (e.g., 601)is different from the second visual indicator (e.g., 620).

In accordance with some embodiments, the first account is a paymentaccount and the second account is a loyalty account. In accordance withsome embodiments, the first account is a payment account and the secondaccount is a payment account.

In accordance with some embodiments, while displaying the second visualindicator (e.g., 620 of a loyalty account): the electronic devicereceives a card code display input, and in response to receiving thecard code display input, the electronic device displays, on the display,visual loyalty card code information (e.g., 624; a barcode or QR code).

In accordance with some embodiments, the user may place the device intoa field of a contactless payment terminal. While displaying the secondvisual indicator: the electronic device receives a request for accountinformation from a contactless payment terminal, and in response toreceiving the request for account information, transmitting, via the oneor more wireless communication elements, account information for thesecond account to the contactless payment terminal, wherein the accountinformation enables the contactless payment terminal to engage in thepayment transaction.

In accordance with some embodiments (e.g., wherein the second account isa payment account), while displaying the second visual indicator andafter transmitting account information for the second account to thecontactless payment terminal: the electronic device receives, via theone or more wireless communication elements, a failure communicationfrom the contactless payment terminal. In response to receiving thefailure communication: the electronic device displays, on the display,an indication that the second account was not accepted and provides anoption to enable the electronic device to participate in the transactionusing an account different from the second account.

In accordance with some embodiments, subsequent to (or in response to)transmitting account information for the second account to thecontactless payment terminal, the electronic device concurrentlydisplays, on the display an indication that the first account and thesecond account were both used during the payment transaction (e.g.,concurrently displaying at least a portion of the first visual indicatorand at least a portion of the second visual indicator).

In accordance with some embodiments, enabling the electronic device toparticipate in the transaction using the first account includesdisplaying a first animation of a ready indicator (e.g., 604) appearingfrom under an image of a card of the first account (e.g., the firstvisual indicator 602). The ready indicator (e.g., 604) indicates thatthe device is enabled to participate in payment transactions using thefirst account. In response to receiving a portion of the one or moreuser swipe inputs, the electronic device displays a second animation ofthe ready indicator to slide the ready indicator (e.g., 604) back underthe image of the card of the first account.

In accordance with some embodiments, the electronic device displays thefirst visual indicator (e.g., 602) identifying the first account priorto enabling the electronic device to participate in the transactionusing the first account via the one or more wireless communicationelements. The electronic device displays, on the display, the secondvisual indicator (e.g., 620) identifying the second account prior toenabling the electronic device to participate in the transaction usingthe second account via the one or more wireless communication elements.

In accordance with some embodiments, one of the first account and thesecond account is a payment account and one of the first account and thesecond account is a loyalty account (e.g., the first account is apayment account and the second account is a loyalty account). The firstvisual indicator (e.g., 602) of the first account has a first dimensioncharacteristic (e.g., size or aspect ratio) and the second visualindicator (e.g., 620) of the second account has a second dimensioncharacteristic different from the first dimension characteristic (e.g.,a different size or different aspect ratio).

In accordance with some embodiments, an electronic wallet of theelectronic device includes payment account information for a pluralityof payment accounts (e.g., including the payment accounts associatedwith 602 and 610) associated with a user of the electronic device.

Note that details of the processes described above with respect tomethod 700 (e.g., FIG. 7 ) are also applicable in an analogous manner tothe methods described below. For example, methods 900, 1100, 1300, 1500,1700, and 1900 may include one or more of the characteristics of thevarious methods described above with reference to method 700. Forexample, the electronic wallet, payment accounts, loyalty accounts,affordances, and inputs of methods 900, 1100, 1300, 1500, 1700, and 1900optionally have one or more of the characteristics of the electronicdevice, payment accounts, loyalty accounts, affordances, and inputs ofthe electronic device described in method 700. For brevity, thesedetails are not repeated below.

FIGS. 8A-8D illustrate exemplary techniques and exemplary userinterfaces for selecting an account, such as a loyalty account or apayment account, for display, in accordance with some embodiments. Forexample, account information of a selected account may subsequently betransmitted to an NFC-enabled payment terminal for use in a transaction(e.g., when the device is placed into a field of the payment terminal).The technique may be performed at an electronic device with a displayand a location sensor. The user interfaces in these figures are used toillustrate the processes described below, including the processes inFIG. 9 .

Some accounts, such as private label accounts or loyalty accounts, maybe associated with particular locations (e.g., a particular merchant ora particular store of a merchant). When at these locations, a user mayprefer to use the associated private label account or loyalty account ina transaction. For example, if a user is at Joe's Electronics store, theuser may prefer to use the private label account associated with Joe'sElectronics store (e.g., a private label credit card account). Foranother example, if a user is at a supermarket, the user may prefer touse the loyalty account associated with the supermarket during thetransaction in which the user makes a payment using a default paymentaccount. Thus, it provides value to a user to display on a display ofthe electronic device visual indications of accounts relevant to thecurrent situation (e.g., location).

For example, a payment account may be associated with multiple locations(e.g., multiple stores in a chain). Additionally, different locationsmay be associated with different payment accounts (e.g., the user has aJoe's Electronics credit card and a Jack's Home Improvement Store creditcard, and the Joe's Electronics credit card may be associated with Joe'sElectronics stores and the Jack's Home Improvement Store card isassociated with Jack's Home Improvement Stores).

Turning now to FIG. 8A, the electronic device detects, using thelocation sensor, a current location (e.g., the electronic devicedetermines that the device is physically located at a particularretailer or a particular store of a particular retailer). The electronicdevice determines whether the current location is associated with afirst account (e.g., determining that a particular private label paymentaccount or a particular loyalty account is associated with theretailer).

As illustrated in FIG. 8A, in accordance with a failure to determine(e.g., during the time between receiving the request to arm the defaultpayment account and arming the default payment account) that the currentlocation is associated with an account other than a default paymentaccount (e.g., the device determines that the location of the device isnot associated with the current location or the device fails todetermine the location of the device), the electronic device displays,on the display, a visual indication 802 of a default payment account(e.g., a visual depiction of a credit card associated with the defaultpayment account). In some embodiments, the visual indication 802 of thedefault payment account is displayed without displaying graphicalindicators for other accounts. At FIG. 8A, the ready indication 804 is avisual indication that the device is ready to participate in atransaction using the default account, represented by visual indicator802.

The visual indication 802 of the default payment account includes: thename of a first financial institution “AA BANK” associated with thedefault payment account, a first background art that corresponds to thebackground art of a payment card associated with the default paymentaccount, at least a portion of an account number associated with thedefault payment account, and an expiration date associated with thedefault payment account.

As illustrated in FIG. 8B, in accordance with a determination that thecurrent location is associated with the first account, the electronicdevice concurrently displays, on the display, the visual indication 802of the default payment account (e.g., a visual depiction of a creditcard associated with the default payment account) and a visualindication 806 of the first account (e.g., a visual depiction of theprivate label card or the particular loyalty account associated with theparticular payment account). The default payment account and the firstaccount are linked to the electronic device (e.g., stored in anelectronic wallet of the device; the electronic device has beenprovisioned for both accounts) and the default payment account and thefirst account are different accounts. At FIG. 8B, the ready indication804 is a visual indication that the device is ready to participate in atransaction using either (or both) the default account, represented byvisual indicator 802, and the first account, represented by visualindicator 806.

The visual indication 806 of the first account may include: the name ofa merchant or financial institution (e.g., “SHOPCO”) associated with thefirst account, a first background art that corresponds to first account,at least a portion of an account number associated with the firstaccount, and an expiration date associated with the first account.

For example, a payment account (e.g., the first account) may beassociated with multiple locations (e.g., multiple stores in a chain).Additionally, different locations may be associated with differentpayment accounts (e.g., the user has a Joe's Electronics credit card anda Jack's Home Improvement Store credit card. The Joe's Electronicscredit card may be associated with Joe's Electronics stores and theJack's Home Improvement Store card is associated with Jack's HomeImprovement Stores).

In accordance with some embodiments, as illustrated in FIG. 8B, thefirst account is a payment account. In some embodiments, the firstaccount is a private label account and the visual indication 806 of thefirst account is an image of the payment card associated with theprivate label account. In some embodiments, the visual indication 806 ofthe first account is displayed partially behind the visual indication802 of the default account.

In accordance with some embodiments, as illustrated in FIG. 8C, thefirst account is a loyalty account. In some embodiments, the firstaccount is a loyalty account and the visual indication 808 is an imageof a loyalty card associated with the loyalty account. In someembodiments, the visual indication 808 of the first account is displayedpartially behind the visual indication 802 of the default account.

In accordance with some embodiments, as illustrated in FIG. 8D, theelectronic device receives a request associated with a paymenttransaction from a contactless payment terminal 820 (e.g., while thedevice is in an NFC field of the contactless payment terminal 820). Theelectronic device determines whether the request includes a request forpayment account information using a first account type corresponding tothe first account (e.g., an NFC-enabled terminal requests a particularretailer's private label credit card when the device is placed into afield of the terminal). In accordance with the determination that thecurrent location is associated with the first account and in accordancewith a determination that the request includes a request for paymentinformation using the first account type, the electronic devicetransmits, using one or more wireless communication elements, paymentaccount information of the first account to the contactless paymentterminal, wherein the payment account information of the first accountenables the contactless payment terminal to engage in the paymenttransaction. In some embodiments, engaging in the payment transactionincludes routing information to one or more financial institutions toverify payment credentials and/or receive authorization to complete thetransaction. For example, the payment account information is transmittedto a contactless payment terminal using NFC. In some embodiments,engaging in the payment transaction includes routing loyalty informationto one or servers for confirmation/authorization of the loyalty account.

In accordance with some embodiments, the electronic device receives arequest associated with a payment transaction from a contactless paymentterminal. The electronic device determines that the request includes arequest for payment account information using a first account typecorresponding to the first account (e.g., an NFC-enabled terminalrequests a particular retailer's private label credit card when thedevice is placed into a field of the terminal). In accordance with thefailure to determine that the current location is associated with anaccount other than the default payment account (and in accordance withdetermination that the request includes a request for payment accountinformation using the first account type), the electronic devicetransmits, using one or more wireless communication elements, paymentaccount information of the default payment account to the contactlesspayment terminal, wherein the payment account information of the defaultpayment account enables the contactless payment terminal to engage inthe payment transaction. In some embodiments, engaging in the paymenttransaction includes routing information to one or more financialinstitutions to verify payment credentials and/or receive authorizationto complete the transaction. For example, the payment accountinformation is transmitted to a contactless payment terminal using NFC.

In accordance with some embodiments, the visual indication of the firstaccount is displayed on the visual indication 802 of the defaultaccount, and wherein the visual indication of the first accountindicates that the first account is enabled to be selected by the devicefor use in a payment transaction without requiring additional userinput. For example, the visual indication of the first account is justtext written on an image of a card of the default account the devicedetermines (at the time of payment) which payment account to use withoutuser intervention.

In accordance with some embodiments, prior to detecting, using thelocation sensor, the current location, the electronic device receives aninput (e.g., a user input) requesting to enable the device for a paymenttransaction (e.g., the user performs a double-click of a hardware button508 of the device which arms the device for making NFC payments and/oraccessing an electronic wallet). In some examples, in response toreceiving the user input requesting to enable the device for a paymenttransaction, the device is enabled to participate in a transaction(e.g., arming the device for making an NFC payment using the defaultpayment account).

In accordance with some embodiments, detecting, using the locationsensor, the current location is in response to receiving the inputrequesting to enable the device for a payment transaction.

In accordance with some embodiments, determining whether the currentlocation is associated with the first account is in response toreceiving an input requesting to enable the device for a paymenttransaction (e.g., the user performs a double-click of a hardware button508 of the device which arms the device for making NFC payments and/oraccessing an electronic wallet). In some examples, in response toreceiving the user input requesting to enable the device for a paymenttransaction, the device is enabled to participate in a transaction(e.g., arming the device for making an NFC payment using the defaultpayment account).

In accordance with some embodiments, a failure to determine that thecurrent location is associated with an account other than a defaultpayment account occurs when the device fails to determine that thecurrent location is associated with a first account before theelectronic device is enabled to participate in a transaction using thedefault payment account via one or more wireless communication elements(e.g., determining whether the current location is associated with afirst account takes longer than enabling the electronic device toparticipate in a transaction using the default payment account via oneor more wireless communication elements). Or, optionally, the electronicdevice concurrently displays, on the display, the visual indication ofthe default payment account and the visual indication of the firstaccount while the device detects that a user of the electronic device isstill looking at the electronic device or that the electronic device isstill facing the user. For example, by only changing the visualindications of the accounts on the display (1) while the user is stilllooking at the device or (2) while the device is still facing the user,the user is provided with the opportunity to view the change andappreciate that a different payment account may be used in the paymenttransactions.

In some embodiments, if the electronic device is worn on a user's wrist,the electronic device may detect that the user is looking at theelectronic device by detecting the user moving the electronic deviceinto a viewing position by raising or rotating their wrist (e.g., araise gesture). The electronic device may detect that the user is nolonger viewing the device by detecting the user lowering their wrist. Asused herein, a viewing position is a position of the electronic devicein which the user can view a display of the electronic device. In someembodiments, the electronic device may detect a signal indicative of auser raising or lowering their wrist as described in U.S. ProvisionalPatent Application Ser. No. 62/026,532, “Raise Gesture Detection in aDevice,” which is hereby incorporated by reference in its entirety.

In some embodiments, a raise gesture detection algorithm can progressthrough a series of states of increasing confidence that a raise gesturehas been performed. For example, a raise-gesture detection algorithm canselect a set of motion-sensor data samples (including accelerometerand/or gyroscopic sensor data) corresponding to a time interval ofinterest (e.g., the amount of time it would likely take a user toexecute a raise gesture). By considering the oldest sample(s) in theset, the algorithm can define a “starting pose,” which can reflect thespatial orientation of the device at the beginning of the time interval.The orientation can be defined relative to an assumed vertical axis ofgravity. Based on the starting pose, the algorithm can determine theamount and/or direction(s) of motion that would likely occur to bringthe device's display into the user's line of sight (also referred to asthe device being brought into a “focus pose”). The likely amount and/ordirection(s) of motion can be expressed as criteria for identifying a“possible” raise gesture, and these criteria can be used to identify,based on some or all of the motion-sensor data samples in the set,whether a possible raise gesture has occurred. The possible raisegesture can be further identified as a “detected” raise gesture bydetermining whether the device, having reached a focus pose, dwells in afocus pose for at least a minimum period of time. A further confirmationcan be performed, if desired, using a gesture classifier. The raisegesture detection algorithm can notify other components of the deviceeach time it identifies a possible, detected, and/or confirmed raisegesture.

In accordance with some embodiments, the electronic device receives arequest for loyalty account information from a contactless paymentterminal, wherein the first account is a loyalty account. In response toreceiving the request for loyalty account information, in accordancewith the failure to determine that the current location is associatedwith an account other than the default payment account (e.g., during thetime between receiving the request to arm the account and arming theaccount) and in accordance with a subsequent determination that thecurrent location is associated with the first account: the electronicdevice transmits, via one or more wireless communication elements,account information for the first account to the contactless paymentterminal, and the electronic device transmits, via the one or morewireless communication elements, payment account information of thedefault payment account to the contactless payment terminal. In someembodiments, the account information for the first account is providedwithout regard to whether a representation of the first account isdisplayed on the display prior to engaging in the payment transaction.In some embodiments, the account information for the first account isprovided only when a representation of the first account is displayed onthe display prior to engaging in the payment transaction.

In accordance with some embodiments, the electronic device receives arequest associated with a payment transaction from a contactless paymentterminal. The electronic device determines that the request includes arequest for payment account information using a first account typecorresponding to the first account, wherein the first account is apayment account that is different from the default payment account(e.g., an NFC-enabled terminal requests a particular retailer's privatelabel credit card when the device is placed into a field of theterminal). In response to receiving the request for account informationin accordance with the failure to determine that the current location isassociated with an account other than the default payment account (e.g.,during the time between receiving the request to arm the account andarming the account) and in accordance with a subsequent determinationthat the current location is associated with the first account: theelectronic device forgoes transmitting, via one or more wirelesscommunication elements, account information for the first account to thecontactless payment terminal, and the electronic device transmits, viathe one or more wireless communication elements, payment accountinformation of the default payment account to the contactless paymentterminal. In some embodiments, account information for the first accountis provided only when a representation of the first account is displayedon the display prior to engaging in the payment transaction.

In accordance with some embodiments, the electronic device receives arequest associated with a payment transaction from a contactless paymentterminal. Prior to receiving the request associated with the paymenttransaction from the contactless payment terminal, the visual indicationof the default payment account (e.g., a visual depiction of a creditcard associated with the default payment account) and the visualindication of the first account (e.g., a visual depiction of the privatelabel card or the particular loyalty account associated with theparticular payment account) were concurrently displayed, on the display.The request includes a request for payment account information using afirst account type corresponding to the first account (e.g., anNFC-enabled terminal requests a particular retailer's private labelcredit card when the device is placed into a field of the terminal). Thefirst account is a payment account of the first account type. Inresponse to receiving the request for account information and inaccordance with the failure to determine that the current location isassociated with an account other than the default payment account (e.g.,during the time between receiving the request to arm the account andarming the account) and in accordance with a subsequent determinationthat the current location is associated with the first account: theelectronic device forgoes transmitting, via one or more wirelesscommunication elements, account information for the default paymentaccount to the contactless payment terminal, and the electronic devicetransmits, via the one or more wireless communication elements, paymentaccount information of the first account to the contactless paymentterminal.

In accordance with some embodiments, in accordance with thedetermination that the current location is associated with the firstaccount, the electronic device receives, via the one or more wirelesscommunication elements, a failure communication from the contactlesspayment terminal (e.g., payment was rejected because the payment accountis suspended by the bank or does not have funds). In response toreceiving the failure communication, the electronic device transmits,via one or more wireless communication elements, account information forthe default payment account to the contactless payment terminal (e.g.,pay with the default card instead). In some embodiments, the deviceconcurrently displays indications of the default payment account andanother payment account to indicate to the user that either paymentaccount might be used in the payment transaction.

In accordance with some embodiments, concurrently displaying, on thedisplay, the visual indication of the default payment account and avisual indication of the first account includes concurrently displaying,on the display, the visual indication of the default payment account ina stack (e.g., above or below the visual indication of the firstaccount) with the visual indication of the first account. In someembodiments, the visual indication of the first account is at leastpartially obscured by the visual indication of the default paymentaccount.

FIG. 9 is a flow diagram illustrating a method 900 for selecting anaccount, such as a loyalty account or a payment account, for display, inaccordance with some embodiments. Method 900 is performed at a device(e.g., 100, 300, 500) with a display and a location sensor. Someoperations in method 900 may be combined, the order of some operationsmay be changed, and some operations may be omitted.

As described below, method 900 provides an intuitive way for selectingan account, such as a loyalty account or a payment account, for display.The method reduces the cognitive burden on a user for selecting anaccount, thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to select an accountfaster and more efficiently conserves power and increases the timebetween battery charges.

At block 902, the electronic device detects, using the location sensor,a current location. At block 904, the electronic device determineswhether the current location is associated with a first account.

At block 904, in accordance with a failure to determine that the currentlocation is associated with an account other than a default paymentaccount, the electronic device displays, on the display, a visualindication (e.g., 802) of a default payment account.

At block 906, in accordance with a determination that the currentlocation is associated with the first account, the electronic deviceconcurrently displays, on the display, the visual indication (e.g., 802)of the default payment account and a visual indication (e.g., 806 ofFIG. 8B; 808 of FIG. 8C) of the first account. The default paymentaccount and the first account are linked to the electronic device andthe default payment account and the first account are different.

In accordance with some embodiments, the first account is a paymentaccount. In some embodiments, the first account is a private labelaccount and the visual indication (e.g., 806) of the first account is animage of the payment card associated with the private label account. Insome embodiments, the visual indication (e.g., 806) of the first accountis displayed partially behind the visual indication (e.g., 802) of thedefault account.

In accordance with some embodiments, the first account is a loyaltyaccount. In some embodiments, the first account is a loyalty account andthe visual indication (e.g., 808) is an image of a loyalty cardassociated with the loyalty account. In some embodiments, the visualindication (e.g., 808) of the first account is displayed partiallybehind the visual indication of the default account.

In accordance with some embodiments, the electronic device receives arequest associated with a payment transaction from a contactless paymentterminal (e.g., while the device is in an NFC field of the contactlesspayment terminal 820). The electronic device determines whether therequest includes a request for payment account information using a firstaccount type corresponding to the first account. In accordance with thedetermination that the current location is associated with the firstaccount and in accordance with a determination that the request includesa request for payment information using the first account type, theelectronic device transmits, using one or more wireless communicationelements, payment account information of the first account to thecontactless payment terminal, wherein the payment account information ofthe first account enables the contactless payment terminal to engage inthe payment transaction. In some embodiments, engaging in the paymenttransaction includes routing information to one or more financialinstitutions to verify payment credentials and/or receive authorizationto complete the transaction. For example, the payment accountinformation is transmitted to a contactless payment terminal using NFC.In some embodiments, engaging in the payment transaction includesrouting loyalty information to one or servers forconfirmation/authorization of the loyalty account.

In accordance with some embodiments, the electronic device receives arequest associated with a payment transaction from a contactless paymentterminal. The electronic device determines that the request includes arequest for payment account information using a first account typecorresponding to the first account. In accordance with the failure todetermine that the current location is associated with an account otherthan the default payment account (and in accordance with determinationthat the request includes a request for payment account informationusing the first account type), the electronic device transmits, usingone or more wireless communication elements, payment account informationof the default payment account to the contactless payment terminal,wherein the payment account information of the default payment accountenables the contactless payment terminal to engage in the paymenttransaction. In some embodiments, engaging in the payment transactionincludes routing information to one or more financial institutions toverify payment credentials and/or receive authorization to complete thetransaction.

In accordance with some embodiments, the visual indication of the firstaccount is displayed on the visual indication (e.g., 802) of the defaultaccount, and wherein the visual indication of the first accountindicates that the first account is enabled to be selected by the devicefor use in a payment transaction without requiring additional userinput.

In accordance with some embodiments, prior to detecting, using thelocation sensor, the current location, the electronic device receives aninput (e.g., a user input) requesting to enable the device for a paymenttransaction.

In accordance with some embodiments, detecting, using the locationsensor, the current location is in response to receiving the inputrequesting to enable the device for a payment transaction.

In accordance with some embodiments, determining whether the currentlocation is associated with the first account is in response toreceiving an input requesting to enable the device for a paymenttransaction (e.g., the user performs a double-click of a hardware button508 of the device which arms the device for making NFC payments and/oraccessing an electronic wallet).

In accordance with some embodiments, a failure to determine that thecurrent location is associated with an account other than a defaultpayment account occurs when the device fails to determine that thecurrent location is associated with a first account before theelectronic device is enabled to participate in a transaction using thedefault payment account via one or more wireless communication elements.

In some embodiments, if the electronic device is worn on a user's wrist,the electronic device may detect that the user is looking at theelectronic device by detecting the user moving the electronic deviceinto a viewing position by raising or rotating their wrist. Theelectronic device may detect that the user is no longer viewing thedevice by detecting the user lowering their wrist. As used herein, aviewing position is a position of the electronic device in which theuser can view a display of the electronic device.

In accordance with some embodiments, the electronic device receives arequest for loyalty account information from a contactless paymentterminal, wherein the first account is a loyalty account. In response toreceiving the request for loyalty account information, in accordancewith the failure to determine that the current location is associatedwith an account other than the default payment account (e.g., during thetime between receiving the request to arm the account and arming theaccount) and in accordance with a subsequent determination that thecurrent location is associated with the first account: the electronicdevice transmits, via one or more wireless communication elements,account information for the first account to the contactless paymentterminal, and the electronic device transmits, via the one or morewireless communication elements, payment account information of thedefault payment account to the contactless payment terminal. In someembodiments, the account information for the first account is providedwithout regard to whether a representation of the first account isdisplayed on the display prior to engaging in the payment transaction.In some embodiments, the account information for the first account isprovided only when a representation of the first account is displayed onthe display prior to engaging in the payment transaction.

In accordance with some embodiments, the electronic device receives arequest associated with a payment transaction from a contactless paymentterminal. The electronic device determines that the request includes arequest for payment account information using a first account typecorresponding to the first account, wherein the first account is apayment account that is different from the default payment account. Inresponse to receiving the request for account information in accordancewith the failure to determine that the current location is associatedwith an account other than the default payment account (e.g., during thetime between receiving the request to arm the account and arming theaccount) and in accordance with a subsequent determination that thecurrent location is associated with the first account: the electronicdevice forgoes transmitting, via one or more wireless communicationelements, account information for the first account to the contactlesspayment terminal, and the electronic device transmits, via the one ormore wireless communication elements, payment account information of thedefault payment account to the contactless payment terminal. In someembodiments, account information for the first account is provided onlywhen a representation of the first account is displayed on the displayprior to engaging in the payment transaction.

In accordance with some embodiments, the electronic device receives arequest associated with a payment transaction from a contactless paymentterminal. Prior to receiving the request associated with the paymenttransaction from the contactless payment terminal, the visual indicationof the default payment account (e.g., 802) and the visual indication ofthe first account (e.g., 806 or 808) were concurrently displayed, on thedisplay. The request includes a request for payment account informationusing a first account type corresponding to the first account (e.g., anNFC-enabled terminal requests a particular retailer's private labelcredit card when the device is placed into a field of the terminal). Thefirst account is a payment account of the first account type. Inresponse to receiving the request for account information and inaccordance with the failure to determine that the current location isassociated with an account other than the default payment account (e.g.,during the time between receiving the request to arm the account andarming the account) and in accordance with a subsequent determinationthat the current location is associated with the first account: theelectronic device forgoes transmitting, via one or more wirelesscommunication elements, account information for the default paymentaccount to the contactless payment terminal, and the electronic devicetransmits, via the one or more wireless communication elements, paymentaccount information of the first account to the contactless paymentterminal.

In accordance with some embodiments, in accordance with thedetermination that the current location is associated with the firstaccount, the electronic device receives, via the one or more wirelesscommunication elements, a failure communication from the contactlesspayment terminal (e.g., payment was rejected because the payment accountis suspended by the bank or does not have funds). In response toreceiving the failure communication, the electronic device transmits,via one or more wireless communication elements, account information forthe default payment account to the contactless payment terminal (e.g.,pay with the default card instead). In some embodiments, the deviceconcurrently displays indications of the default payment account andanother payment account to indicate to the user that either paymentaccount might be used in the payment transaction.

In accordance with some embodiments, concurrently displaying, on thedisplay, the visual indication of the default payment account and avisual indication of the first account includes concurrently displaying,on the display, the visual indication (e.g., 802) of the default paymentaccount in a stack (e.g., above or below the visual indication of thefirst account) with the visual indication (e.g., 806, 808) of the firstaccount. In some embodiments, the visual indication (e.g., 806, 808) ofthe first account is at least partially obscured by the visualindication (e.g., 802) of the default payment account.

Note that details of the processes described above with respect tomethod 900 (e.g., FIG. 9 ) are also applicable in an analogous manner tothe methods described above and below. For example, methods 700, 1100,1300, 1500, 1700, and 1900 may include one or more of thecharacteristics of the various methods described above with reference tomethod 900. For example, the electronic wallet, payment accounts,loyalty accounts, affordances, and inputs of methods 700, 1100, 1300,1500, 1700, and 1900 optionally have one or more of the characteristicsof the electronic device, payment accounts, loyalty accounts,affordances, and inputs of the electronic device described in method900. For brevity, these details are not repeated below.

FIGS. 10A-10E illustrate exemplary techniques and exemplary userinterfaces for selecting an account, such as a loyalty account or apayment account, for display from among multiple accounts in anelectronic wallet, in accordance with some embodiments. For example,account information of a selected account may subsequently betransmitted to an NFC-enabled payment terminal for use in a transaction(e.g., when the device is placed into a field of the payment terminal).The technique is performed at an electronic device with a display, alocation sensor, and one or more wireless communication elements. Theuser interfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 11 .

The electronic device receives an input (e.g., a user input) requestingto enable the device for a payment transaction (e.g., the user performsa double-click of a hardware button 508 of the device to arm the devicefor making NFC payments).

In response to receiving the input, the electronic device detects, usingthe location sensor, a current location (e.g., determining that thedevice is physically located at a particular retailer or a particularstore of a particular retailer). The electronic device also determineswhether a set of one or more payment criteria have been met, wherein theset of one or more payment criteria includes a criterion that is metwhen the current location is associated with a first payment account(e.g., determining that a particular private label payment account isassociated with the retailer).

As illustrated in FIG. 10A, in accordance with a determination that theset of one or more payment criteria is not met, the electronic devicedisplays, on the display, a visual indication 1002 of a default paymentaccount, wherein the default payment account is different from the firstpayment account (e.g., a visual depiction 1002 of a credit cardassociated with the default payment account, and forgoes displaying anindication of the first payment account).

The device may also display, on the display, an indication 1006 thatother accounts are also available or an indication 1006 of the number ofother accounts available. In this example, the indication 1006 includesfour paging dots. The first paging dot is of a first color that isdifferent from a second color of the second, third, and fourth pagingdots. The four paging dots indicate that a total of four accounts areavailable. The first paging dot being a different color from the otherpaging dots indicates that the device is currently displayinginformation (e.g., visual indication 1002) corresponding to the defaultpayment account.

The device may also display, on the display, ready indication 1004.Ready indication 1004 is a visual indication that the device is enabledto participate in a transaction using the default payment account, whichis represented by visual indication 1002. Visual indication 1002 mayinclude: the name of a financial institution “AA BANK” associated withthe default payment account, a background art that corresponds to thebackground art of a payment card associated with the default paymentaccount, at least a portion of an account number associated with thedefault payment account, and an expiration date associated with thedefault payment account.

As illustrated in FIG. 10B, in accordance with a determination that theset of one or more payment criteria is met, the electronic devicedisplays, on the display, a visual indication 1008 of the first paymentaccount (and forgoes displaying an indication of the default paymentaccount).

The device may also display, on the display, ready indication 1010.Ready indication 1010 is a visual indication that the device is enabledto participate in a transaction using the first payment account, whichis represented by visual indication 1008. Visual indication 1008 mayinclude: the name of a merchant “SHOPCO” associated with the firstpayment account, a background art that corresponds to the background artof a private label card associated with the first payment account, atleast a portion of an account number associated with the first paymentaccount, and an expiration date associated with the first paymentaccount.

In accordance with some embodiments, in accordance with thedetermination that the set of one or more payment criteria is met, theelectronic device enables the electronic device to participate in atransaction using the first payment account via the one or more wirelesscommunication elements. Additionally, the electronic device may forgoenabling the electronic device to participate in a transaction using thedefault payment account.

In accordance with some embodiments, in accordance with thedetermination that the set of one or more payment criteria is not met,the electronic device enables the electronic device to participate in atransaction using the default payment account via the one or morewireless communication elements. Additionally, the electronic device mayforgo enabling the electronic device to participate in a transactionusing the first payment account.

In accordance with some embodiments, in accordance with thedetermination that the set of one or more payment criteria is not met,the electronic device forgoes displaying, on the display, the visualindication of the first payment account (e.g., displaying the visualindication of the default payment account without displaying the visualindication of the first payment account).

In accordance with some embodiments, the electronic device includes atouch-sensitive surface. As illustrated in FIG. 10C, the electronicdevice receives one or more inputs in a first direction (e.g., receivingone or more left swipes or right swipes via the touch-sensitive surfaceor detecting a change in device orientation in the first direction). Asillustrated in FIG. 10D, in response to receiving the one or moreinputs: the electronic device displays, on the display, a second visualindicator 1012 identifying (e.g., that identifies) a second accountdifferent from the first payment account and the default paymentaccount. The electronic device enables the electronic device toparticipate in a transaction using the second account via the one ormore wireless communication elements (e.g., arming the device for makingan NFC transaction using the second account and disabling the devicefrom participating in transactions using the first account). Thus, whenthe device presents a payment account, the user can provide input tochange to a payment account (e.g., select a payment account from among aplurality of payment accounts in an electronic wallet of the device).

In accordance with some embodiments, the electronic device receives arequest for account information from a contactless payment terminal(e.g., when the device detects that a user has placed the device into afield of an NFC-enabled contactless payment terminal). In response toreceiving the request for account information, the electronic devicetransmits, via the one or more wireless communication elements, accountinformation for a respective enabled account to the contactless paymentterminal (e.g., whichever account for which the device is enabled toparticipate in payment transactions; whichever account is currentlydisplayed), wherein the account information enables the contactlesspayment terminal to engage in the payment transaction. In someembodiments, engaging in the payment transaction includes routinginformation to one or more financial institutions to verify paymentcredentials and/or receive authorization to complete the transaction(e.g., if account information for a payment account is transmitted tothe terminal). For example, the payment account information istransmitted to a contactless payment terminal using NFC. In someembodiments, engaging in the payment transaction includes routingloyalty information to one or servers for confirmation/authorization ofthe loyalty account (e.g., if account information for a loyalty accountis transmitted to the terminal).

In accordance with some embodiments, the set of one or more criteriaincludes a criterion that is met when the device is authorized to use(e.g., without user confirmation) the first payment account (e.g., tooverride the default payment account) for transactions at the currentlocation.

In accordance with some embodiments, the electronic device determinesthat the current location is associated with a loyalty account. Theelectronic device concurrently displays, on the display, a visualindication of the loyalty account along with a respective visualindication of a payment account (e.g., along with the visual indicationof the default payment account or the first payment account). Thus, ifthe availability of an appropriate loyalty card is detected, the devicedisplays the indication of the default payment card (or the privatelabel card) along with the indication of the loyalty card.

In accordance with some embodiments, the electronic device includes oneor more input devices. Prior to receiving the user input requesting toenable the device for a payment transaction: the electronic devicereceives a request (e.g., manual entry, importing from a server, orinput using a camera sensor of the electronic device) to link a paymentaccount with the electronic device. The request comprising accountinformation (e.g., card number, card expiration date, name on card) ofthe payment account. The electronic device links the payment accountwith the electronic device; (e.g., adding the payment account to anelectronic wallet on the electronic device). The electronic devicedetermines that a financial institution associated with the paymentaccount has authorized the payment account for selection based onlocation without requiring user input. The electronic device receivesuser input activating the payment account for selection based onlocation without requiring user input, as illustrated in FIG. 10E.

As illustrated in FIG. 10E, a user can activate a payment account to beused for location-based selection by activating the yes affordance 1030.Alternatively, a user can forgo activating the payment account forlocation-based selection by activating the no affordance 1032. In someembodiments, the option to activate a payment account for selectionbased on location is displayed during the setup of a card (e.g., duringor right after the card is linked to the electronic device).Alternatively (or in addition), the financial institution can authorizea payment account for selection based on location (without requiringuser input) at a time after the payment account has been linked to theelectronic device. In that situation, a new option can appear in asetting menu for the payment account. Similarly, the device can displaya pop-up notification when the devices detects that a payment is made.The notification indicates that the payment account is now capable oflocation-based selection. Subsequently, the user can elect to activate(or not activate) the feature for selection based on location withoutrequiring user input.

In accordance with some embodiments, in accordance with thedetermination that the set of one or more payment criteria is met, theelectronic device enables the electronic device to participate in atransaction using the first payment account via the one or more wirelesscommunication elements. The electronic device receives a requestassociated with a payment transaction from a contactless paymentterminal. The electronic device determines whether the request includesa request for payment account information using an account typecorresponding to a second payment account different from the firstpayment account (e.g., an NFC-enabled terminal requests a particularretailer's private label credit card when the device is placed into afield of the terminal). In accordance with a determination that therequest includes a request for payment information using the secondaccount type, the electronic device provides a notification (e.g.,visual, audio, or haptic) requesting authorization to transmit, usingone or more wireless communication elements, payment account informationof the second account to the contactless payment terminal, wherein thepayment account information of the second account enables thecontactless payment terminal to engage in the payment transaction. Thus,when the device determines that a first payment account is appropriatefor a particular location, but the contactless payment terminal requestspayment using a different payment account, the user is notified andrequested to provide authorization to proceed with the paymenttransaction using the second payment account.

FIG. 11 is a flow diagram illustrating a method 1100 for selecting anaccount, such as a loyalty account or a payment account, for displayfrom among multiple accounts in an electronic wallet in accordance withsome embodiments. Method 1100 is performed at a device (e.g., 100, 300,500) with a display and a location sensor. Some operations in method1100 may be combined, the order of some operations may be changed, andsome operations may be omitted.

As described below, method 1100 provides an intuitive way for selectingan account. The method reduces the cognitive burden on a user forselecting an account for display and/or payment, thereby creating a moreefficient human-machine interface. For battery-operated computingdevices, enabling a user to select an account faster and moreefficiently conserves power and increases the time between batterycharges.

At block 1102, the electronic device receives an input (e.g., a userinput) requesting to enable the device for a payment transaction (e.g.,the user performs a double-click of a hardware button 508 of the deviceto arm the device for making NFC payments).

At block 1104, in response to receiving the input, the techniquecontinues to block 1106. At block 1106, the electronic device detects,using the location sensor, a current location (e.g., determining thatthe device is physically located at a particular retailer or aparticular store of a particular retailer).

At block 1108, the electronic device determines whether a set of one ormore payment criteria have been met, wherein the set of one or morepayment criteria includes a criterion that is met when the currentlocation is associated with a first payment account (e.g., determiningthat a particular private label payment account is associated with theretailer).

At block 1110, in accordance with a determination that the set of one ormore payment criteria is not met, the electronic device displays, on thedisplay, a visual indication (e.g., 1002) of a default payment account,wherein the default payment account is different from the first paymentaccount (e.g., a visual depiction of a credit card associated with thedefault payment account, and forgoing displaying an indication of theparticular payment account).

In accordance with some embodiments, at block 1112, in accordance withthe determination that the set of one or more payment criteria is notmet, the electronic device enables the electronic device to participatein a transaction using the default payment account via the one or morewireless communication elements.

At block 1114, in accordance with a determination that the set of one ormore payment criteria is met, the electronic device displays, on thedisplay, a visual indication (e.g., 1008) of the first payment account(and forgoes displaying an indication of the default payment account).

In accordance with some embodiments, at block 1116, in accordance withthe determination that the set of one or more payment criteria is met,the electronic device enables the electronic device to participate in atransaction using the first payment account via the one or more wirelesscommunication elements.

In accordance with some embodiments, in accordance with thedetermination that the set of one or more payment criteria is not met,the electronic device forgoes displaying, on the display, the visualindication (e.g., 1008) of the first payment account (e.g., displayingthe visual indication of the default payment account without displayingthe visual indication of the first payment account).

In accordance with some embodiments, the electronic device includes atouch-sensitive surface. The electronic device receives one or moreinputs in a first direction (e.g., one or more left swipes or rightswipes via the touch-sensitive surface or detecting a change in deviceorientation in the first direction). In response to receiving the one ormore inputs, the electronic device displays, on the display, a secondvisual indicator (e.g., 1012) identifying a second account differentfrom the first payment account and the default payment account, and theelectronic device enables the electronic device to participate in atransaction using the second account via the one or more wirelesscommunication elements (e.g., arming the device for making an NFCtransaction using the second account and disabling the device fromparticipating in transactions using the first account).

In accordance with some embodiments, the electronic device receives arequest for account information from a contactless payment terminal. Inresponse to receiving the request for account information, theelectronic device transmits, via the one or more wireless communicationelements, account information for a respective enabled account to thecontactless payment terminal, wherein the account information enablesthe contactless payment terminal to engage in the payment transaction.In some embodiments, engaging in the payment transaction includesrouting information to one or more financial institutions to verifypayment credentials and/or receive authorization to complete thetransaction (e.g., if account information for a payment account istransmitted to the terminal).

In accordance with some embodiments, the set of one or more criteriaincludes a criterion that is met when the device is authorized to use(e.g., without user confirmation) the first payment account (e.g., tooverride the default payment account) for transactions at the currentlocation.

In accordance with some embodiments, the electronic device determinesthat the current location is associated with a loyalty account. Theelectronic device concurrently displays, on the display, a visualindication of the loyalty account along with a respective visualindication of a payment account (e.g., along with the visual indicationof the default payment account or the first payment account). Thus, ifthe availability of an appropriate loyalty card is detected, the devicedisplays the indication of the default payment card (or the privatelabel card) along with the indication of the loyalty card.

In accordance with some embodiments, the electronic device includes oneor more input devices. Prior to receiving the user input requesting toenable the device for a payment transaction: the electronic devicereceives a request (e.g., manual entry, importing from a server, orinput using a camera sensor of the electronic device) to link a paymentaccount with the electronic device. The request comprising accountinformation (e.g., card number, card expiration date, name on card) ofthe payment account. The electronic device links the payment accountwith the electronic device; (e.g., adding the payment account to anelectronic wallet on the electronic device). The electronic devicedetermines that a financial institution associated with the paymentaccount has authorized the payment account for selection based onlocation without requiring user input. The electronic device receivesuser input activating the payment account for selection based onlocation without requiring user input.

In accordance with some embodiments, in accordance with thedetermination that the set of one or more payment criteria is met, theelectronic device enables the electronic device to participate in atransaction using the first payment account via the one or more wirelesscommunication elements. The electronic device receives a requestassociated with a payment transaction from a contactless paymentterminal. The electronic device determines whether the request includesa request for payment account information using an account typecorresponding to a second payment account different from the firstpayment account (e.g., an NFC-enabled terminal requests a particularretailer's private label credit card when the device is placed into afield of the terminal). In accordance with a determination that therequest includes a request for payment information using the secondaccount type, the electronic device provides a notification (e.g.,visual, audio, or haptic) requesting authorization to transmit, usingone or more wireless communication elements, payment account informationof the second account to the contactless payment terminal, wherein thepayment account information of the second account enables thecontactless payment terminal to engage in the payment transaction. Thus,when the device determines that a first payment account is appropriatefor a particular location, but the contactless payment terminal requestspayment using a different payment account, the user is notified andrequested to provide authorization to proceed with the paymenttransaction using the second payment account.

Note that details of the processes described above with respect tomethod 1100 (e.g., FIG. 11 ) are also applicable in an analogous mannerto the methods described above and below. For example, methods 700, 900,1300, 1500, 1700, and 1900 may include one or more of thecharacteristics of the various methods described above with reference tomethod 1100. For example, the electronic wallet, payment accounts,loyalty accounts, affordances, and inputs of methods 700, 900, 1300,1500, 1700, and 1900 optionally have one or more of the characteristicsof the electronic device, payment accounts, loyalty accounts,affordances, and inputs of the electronic device described in method1100. For brevity, these details are not repeated below.

FIGS. 12A-12D illustrate exemplary techniques and exemplary userinterfaces for transmitting account information of an account selectedfrom among multiple accounts in an electronic wallet, in accordance withsome embodiments. The technique is performed at an electronic devicewith a display and one or more wireless communication elements (e.g.,one or more wireless antennas such as NFC antennas, WiFi antennas.). Theuser interfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 13 .

The electronic device receives an input (e.g., user input) requesting toenable the device for a payment transaction (e.g., the user performs adouble-click of a hardware button of the device to arm the device formaking NFC payments). At FIG. 12A, in response to receiving the input,the electronic device displays, on the display, a payment indication(e.g., 1202) that represents a plurality of payment accounts including afirst payment account and a second payment account (e.g., display a“smart selection” indication that does not identify a particular paymentaccount).

As illustrated in FIG. 12B, a user places the electronic device 500 intoan NFC field of a contactless payment terminal 1220. The electronicdevice receives, via the one or more wireless communication elements, arequest for account information corresponding to a payment transaction(e.g., received from the contactless payment terminal 1220).

In response to receiving the request for account informationcorresponding to the payment transaction, in accordance with adetermination that payment criteria for a first payment account havebeen met (e.g., the first payment account is associated with a currentlocation of the device), the electronic device transmits, via the one ormore wireless communication elements, account information for the firstpayment account without transmitting account information for the secondpayment account (and, optionally, without transmitting payment accountinformation for any other payment account associated with the paymentindication other than the first payment account). In response toreceiving the request for account information corresponding to thepayment transaction, in accordance with a determination that paymentcriteria for the second payment account have been met (e.g., the secondpayment account is associated with a current location of the device),the electronic device transmits, via the one or more wirelesscommunication elements, account information for the second paymentaccount without transmitting account information for the first paymentaccount (and, optionally, without transmitting payment accountinformation for any other payment account associated with the paymentindication other than the second payment account). Thus, a user can seea visual indication that the “smart selection” feature is selected. Whenthe device detects an attempt to make a payment, the electronic devicetransmits account information for an appropriate account.

In accordance with some embodiments, the electronic device is configuredto enable payment using one of a default payment account and a pluralityof non-default payment accounts (e.g., payment accounts that are onlyused when payment criteria corresponding to the respective paymentaccount are met). In accordance with a determination that paymentcriteria have not been met for any of the non-default payment accounts,the electronic device transmits, via the one or more wirelesscommunication elements, account information for the default paymentaccount without transmitting account information for the non-defaultpayment accounts.

In accordance with some embodiments, the payment criteria include acriterion based on a determination associated with a current location ofthe electronic device. For example, the criteria are met when theelectronic device is within a determined geographical area. For anotherexample, the criteria are not met when the electronic device is notwithin a determined geographical area.

In accordance with some embodiments, as illustrated in FIG. 12A, thepayment indication 1202 that represents the plurality of paymentaccounts does not include an indication of the first payment account anddoes not include an indication of the second payment account. Forexample, there is no indication on the display that indicates the firstor second payment accounts. The payment indication 1202 that representsthe plurality of payment accounts does not look like a credit card anddoes not look like the indication of the first payment account or theindication of the second payment account. Thus, a user can understand ata glance that the device is in a special mode of operation.

In accordance with some embodiments, the plurality of payment accountsonly include payment accounts for which the electronic device hasreceived user input activating selection based on location withoutrequiring user input.

In accordance with some embodiments, the plurality of payment accountsonly include payment accounts for which a financial institutionassociated with the payment account has authorized the respectivepayment account for selection based on location without requiring userinput.

In accordance with some embodiments, a contextual-selection mode ofoperation in which the device selects, based on context, which of theplurality of payment accounts to use for a payment transaction isrepresented as a selectable payment option. In some embodiments, thedevice receives selection of the selectable payment option and inresponse to selection of the selectable payment option, switches to acontextual-selection mode of operation.

In FIG. 12C, in accordance with some embodiments, the electronic deviceincludes a touch-sensitive surface. For example, prior to making apayment as illustrated in FIG. 12B, the electronic device receives oneor more inputs (e.g., user inputs) in a first direction (e.g., one ormore left swipes or right swipes via the touch-sensitive surface or achange in orientation of the device in the first direction). Asillustrated in FIG. 12C, the electronic device may display an animationthat includes transitioning the payment indication 1202 off the display.In response to receiving the one or more inputs, the electronic devicereplaces, on the display, the payment indication 1202 that representsthe plurality of payment accounts with a second visual indicator 1220different from the payment indication 1202 that represents the pluralityof payment accounts, wherein the second visual selection indicatoridentifies a third payment account different from the first paymentaccount and the second payment account. In response to receiving the oneor more inputs, the electronic device enables the electronic device toparticipate in a transaction using the third payment account via the oneor more wireless communication elements. (e.g., arming the device formaking an NFC transaction using the second account and disabling thedevice from participating in transactions using the first account).Thus, the user can select a specific payment account. Once the userselects a specific payment account, the user can make a payment usingthat account, as illustrated in FIG. 12B.

In accordance with some embodiments, the payment indication 1202 thatrepresents the plurality of payment accounts is different from thevisual indicators (e.g., 1220) of individual payment accounts of theplurality of payment accounts. For example, the payment indication 1202includes a logo without a surrounding card, while all other paymentaccounts are represented by card images (e.g., visual indication 1220),or the payment indication is accompanied by text that indicates that itrepresents contextual-selection between a plurality of different paymentaccounts (e.g., “AUTO SELECT”).

FIG. 13 is a flow diagram illustrating a method for transmitting accountinformation of an account selected from among multiple accounts in anelectronic wallet, in accordance with some embodiments. Method 1300 isperformed at a device (e.g., 100, 300, 500) with a display and one ormore wireless communication elements. Some operations in method 1300 maybe combined, the order of some operations may be changed, and someoperations may be omitted.

As described below, method 1300 provides an intuitive way fortransmitting account information of an account selected from amongmultiple accounts in an electronic wallet. The method reduces thecognitive burden on a user for selecting an account for use in apayment, thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to select an accountfaster and more efficiently conserves power and increases the timebetween battery charges.

At block 1302, the electronic device receives an input (e.g., userinput) requesting to enable the device for a payment transaction (e.g.,the user performs a double-click of a hardware button 508 of the deviceto arm the device for making NFC payments).

At block 1304, in response to receiving the input, the electronic devicedisplays, on the display, a payment indication (e.g., 1202) thatrepresents a plurality of payment accounts including a first paymentaccount and a second payment account (e.g., display a “smart selection”indication that does not identify a particular payment account).

At block 1306, the electronic device receives, via the one or morewireless communication elements, a request for account informationcorresponding to a payment transaction; (e.g., received from acontactless payment terminal 1220).

At block 1308, in response to receiving the request for accountinformation corresponding to the payment transaction, the techniqueproceeds to blocks 1310-1312. At block 1310, in accordance with adetermination that payment criteria for a first payment account havebeen met, the electronic device transmits, via the one or more wirelesscommunication elements, account information for the first paymentaccount without transmitting account information for the second paymentaccount (and, optionally, without transmitting payment accountinformation for any other payment account associated with the paymentindication other than the first payment account).

At block 1312, in accordance with a determination that payment criteriafor the second payment account have been met, transmitting, via the oneor more wireless communication elements, account information for thesecond payment account without transmitting account information for thefirst payment account (and, optionally, without transmitting paymentaccount information for any other payment account associated with thepayment indication other than the second payment account).

In accordance with some embodiments, the electronic device is configuredto enable payment using one of a default payment account and a pluralityof non-default payment accounts (e.g., payment accounts that are onlyused when payment criteria for the payment account are met). Inaccordance with a determination that payment criteria have not been metfor any of the non-default payment accounts, the electronic devicetransmits, via the one or more wireless communication elements, accountinformation for the default payment account without transmitting accountinformation for the non-default payment accounts.

In accordance with some embodiments, the payment criteria include acriterion based on a determination associated with a current location ofthe electronic device. For example, the criteria are met when theelectronic device is within a determined geographical area. For anotherexample, the criteria are not met when the electronic device is notwithin a determined geographical area.

In accordance with some embodiments, the payment indication (e.g., 1202)that represents the plurality of payment accounts does not include anindication of the first payment account and does not include anindication of the second payment account.

In accordance with some embodiments, the plurality of payment accountsonly include payment accounts for which the electronic device hasreceived user input activating selection based on location withoutrequiring user input.

In accordance with some embodiments, the plurality of payment accountsonly include payment accounts for which a financial institutionassociated with the payment account has authorized the respectivepayment account for selection based on location without requiring userinput.

In accordance with some embodiments, a contextual-selection mode ofoperation in which the device selects, based on context, which of theplurality of payment accounts to use for a payment transaction isrepresented as a selectable payment option. In some embodiments, thedevice receives selection of the selectable payment option and inresponse to selection of the selectable payment option, switches to acontextual-selection mode of operation.

In accordance with some embodiments, the electronic device includes atouch-sensitive surface. The electronic device receives one or moreinputs (e.g., user inputs) in a first direction (e.g., one or more leftswipes or right swipes via the touch-sensitive surface or a change inorientation of the device in the first direction). In response toreceiving the one or more inputs, the electronic device replaces, on thedisplay, the payment indication (e.g., 1202) that represents theplurality of payment accounts with a second visual indicator (e.g.,1220) different from the payment indication (e.g., 1202) that representsthe plurality of payment accounts, wherein the second visual selectionindicator identifies a third payment account different from the firstpayment account and the second payment account. In response to receivingthe one or more inputs, the electronic device enables the electronicdevice to participate in a transaction using the third payment accountvia the one or more wireless communication elements. Thus, the user canselect a specific payment account.

In accordance with some embodiments, the payment indication (e.g., 1202)that represents the plurality of payment accounts is different from thevisual indicators (e.g., 1220) of individual payment accounts of theplurality of payment accounts.

Note that details of the processes described above with respect tomethod 1300 (e.g., FIG. 13 ) are also applicable in an analogous mannerto the methods described above and below. For example, methods 700, 900,1100, 1500, 1700, and 1900 may include one or more of thecharacteristics of the various methods described above with reference tomethod 1300. For example, the electronic wallet, payment accounts,loyalty accounts, affordances, and inputs of methods 700, 900, 1100,1500, 1700, and 1900 optionally have one or more of the characteristicsof the electronic device, payment accounts, loyalty accounts,affordances, and inputs of the electronic device described in method1300. For brevity, these details are not repeated below.

FIGS. 14A-14E illustrate exemplary techniques and exemplary userinterfaces for receiving a selection of an account from among multipleaccounts in an electronic wallet, in accordance with some embodiments.For example, account information of a selected account may subsequentlybe transmitted to an NFC-enabled payment terminal for use in atransaction (e.g., when the device is placed into a field of the paymentterminal). The technique is performed at an electronic device with adisplay, a touch-sensitive surface configured to detect intensity ofcontacts, and one or more wireless communication elements. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 15 .

The electronic device receives a first input (e.g., user input at ahardware button). For example, the user double-clicks a mechanical orcapacitive button 508 of the device.

As illustrated in FIG. 14A, in response to receiving the first input,the electronic device displays, on the display, a first user interface(e.g., the user interface of FIG. 14A), wherein the first user interfaceincludes a first visual indicator 1402 identifying a payment cardassociated with multiple payment accounts, and a second visual indicator1406 identifying a first payment account (e.g., a savings account) ofthe multiple payment accounts of the payment card. As illustrated inFIG. 14A, the second visual indicator 1406 may include “Savings Account”to indicate that the savings account of the payment card is active orselected. The first visual indicator 1402 may include one or more of:the name of the financial institution that services the payment account;an account number; an expiration date; and background art.

The electronic device enables the electronic device to use the firstpayment account to engage in a payment transaction via the one or morewireless communication elements. For example, once enabled for the firstpayment account, a user can place the electronic device into a field ofa contactless payment terminal to make an NFC payment using the firstpayment account. In FIG. 14A, ready indication 1404 is a visualindication that the device is enabled to participate in a paymenttransaction using the first payment account.

As illustrated in FIG. 14B, the electronic devices detects a firstcontact on the touch-sensitive surface. The electronic device determineswhether a characteristic intensity of the first contact is above anintensity threshold.

As illustrated in FIGS. 14C and 14D, in accordance with a determinationthat the characteristic intensity of the first contact is above theintensity threshold (e.g., hard press), the electronic device displays,on the display, a second user interface, wherein the second userinterface enables selection between different payment accountsrepresented by the first visual indicator. For example, the hard presscan result in the display of the user interface of FIG. 14D. For anotherexample, the hard press can result in the display of FIG. 14C, afterwhich activation of affordance 1412 at the user interface of FIG. 14Cresults in the display of the user interface of FIG. 14D.

There are multiple ways for the user to access the user interface thatallows selection from among the multiple payment accounts of the paymentcard. One method is to enable the electronic device to engage in apayment transaction (e.g., using an electronic wallet application), thusresulting in the first visual indicator to be displayed while the deviceis in a payment mode, as discussed above. Another method is to accessthe settings or details of a particular payment account from anelectronic wallet application, thus resulting in the first visualindicator being displayed while the device is not in a payment mode(e.g., not enabled to engage in a payment transaction via the one ormore wireless communication elements). While displaying the userinterface (and not in the payment mode), the device detects a contact onthe touch-sensitive surface; the device determines whether acharacteristic intensity of the contact is above an intensity threshold;and in accordance with a determination that the characteristic intensityof the contact is above the intensity threshold (e.g., hard press), thedevice displays, on the display, an additional user interface, whereinthe additional user interface enables selection between differentpayment accounts represented by the first visual indicator. Both ofthese methods (via payment mode and non-payment mode) allow the user tobring up the account selection interface to select from among themultiple payment accounts of a payment card.

As illustrated in FIG. 14C, in accordance with some embodiments, thesecond user interface includes a payment account selection affordance1412. The electronic device detects a second contact at a location onthe touch-sensitive surface corresponding to the payment accountselection affordance 1412. As illustrated in FIG. 14D, in response todetecting the second contact, the electronic device displays, on thedisplay, a third user interface 1418, wherein the third user interface1418 includes one or more account affordances (e.g., 1420, 1422, 1424)corresponding to at least some of the multiple payment accounts. Theelectronic device detects a third contact at a location associated withan account affordance 1424 of the one or more account affordances (e.g.,1420, 1422, 1424), wherein the account affordance 1424 corresponds to asecond payment account (e.g., a credit account) of the multiple paymentaccounts and the second payment account is different from the firstpayment account. In some examples, when the electronic device detectsactivation of cancel affordance 1426, the electronic device displays theuser interface of FIG. 14C.

As illustrated in FIG. 14E, in response to detecting the third contact,the electronic device displays, on the display, a fourth user interface(e.g., the user interface of FIG. 14E), wherein the fourth userinterface includes: the first visual indicator 1402 identifying thepayment card associated with multiple payment accounts (e.g., thepayment card has not changed), and a third visual indicator 1430identifying the second payment account (e.g., a credit account differentfrom the checking account) of the multiple payment accounts of thepayment card. For example, the third visual indicator 1430 says “CreditAccount” to indicate that the credit account of the payment card isactive or selected. In response to detecting the third contact, theelectronic device also enables the electronic device to use the secondpayment account to engage in a payment transaction via the one or morewireless communication elements (and disables the electronic device fromusing the first payment account to engage in a payment transaction). Forexample, a user can place the electronic device into a field of acontactless payment terminal to make an NFC payment using the firstpayment account. For example, ready indication 14032 is a visualindication that the device is enabled to participate in a paymenttransaction using the second payment account.

In accordance with some embodiments, in accordance with a determinationthat the characteristic intensity of the first contact is below theintensity threshold (e.g., a light press), the electronic devicemaintains display of the first visual indicator 1402 (and, optionally,the second visual indicator 1406) without displaying, on the display,the second user interface.

In accordance with some embodiments, the one or more account affordances1420, 1422, 1424 include a plurality of account affordances.

In accordance with some embodiments, a visual indicator (e.g., 1420,1422, 1424) of a currently selected payment account is highlighted(e.g., different color, displayed with a check mark 1428, etc.) on thesecond user interface.

In accordance with some embodiments, detecting the second contactincludes determining that a characteristic intensity of the secondcontact is not above an intensity threshold (e.g., it is not a hardpress).

In accordance with some embodiments, the second user interface includesa payment account deletion affordance 1410. The electronic devicedetects activation of the payment account deletion affordance 1410. Inresponse to detecting activation of the payment account deletionaffordance 1410, the electronic device removes (e.g., unlinking from theelectronic device) the multiple payment accounts of the payment cardfrom an electronic wallet of the device.

In accordance with some embodiments, the payment account deletionaffordance 1410 includes one or more visual characteristicsdifferentiating the payment account deletion affordance from the paymentaccount selection affordance 1412. For example, the affordances have adifferent shape, a different fill color, or different text to helpprevent a user from mistaking one affordance for the other.

In accordance with some embodiments, while displaying, on the display,the fourth user interface, the electronic device detects a swipe input(e.g., horizontal swipe input) on the touch-sensitive surface. In someembodiments, the swipe input has a characteristic intensity below theintensity threshold. In response to detecting the swipe input, theelectronic device displays a fifth user interface, wherein the fifthuser interface includes a fourth visual indicator identifying a secondpayment card different from the payment card. Thus, the user can swipeto change payment cards.

In accordance with some embodiments, the first user interface, thesecond user interface, the third user interface, and the fourth userinterface are user interfaces of a single electronic wallet application,the single electronic wallet application including a plurality ofpayment accounts associated with a user of the electronic device.

In accordance with some embodiments, the electronic device receives arequest for account information from a contactless payment terminal. Inresponse to receiving the request for account information, theelectronic device transmits, via the one or more wireless communicationelements, account information for the second payment account to thecontactless payment terminal, wherein the account information enablesthe contactless payment terminal to engage in a payment transaction. Insome embodiments, engaging in the payment transaction includes routinginformation to one or more financial institutions to verify paymentcredentials and/or receive authorization to complete the transaction.For example, the payment account information is transmitted to acontactless payment terminal using NFC.

FIG. 15 is a flow diagram illustrating a method for receiving aselection of an account from among multiple accounts in an electronicwallet, in accordance with some embodiments. Method 1500 is performed ata device (e.g., 100, 300, 500) with a display, a touch-sensitive surfaceconfigured to detect intensity of contacts, and one or more wirelesscommunication elements. Some operations in method 1500 may be combined,the order of some operations may be changed, and some operations may beomitted.

As described below, method 1500 provides an intuitive way for receivinga selection of an account from among multiple accounts in an electronicwallet. The method reduces the cognitive burden on a user for selectingan account, thereby creating a more efficient human-machine interface.For battery-operated computing devices, enabling a user to select anaccount faster and more efficiently conserves power and increases thetime between battery charges.

At block 1502, the electronic device receives a first input (e.g., userinput at a hardware button). For example, the user double-clicks amechanical or capacitive button of the device.

At block 1504, in response to receiving the first input, the techniqueproceeds to 1506. At block 1506, the electronic device displays, on thedisplay, a first user interface (e.g., user interface of FIG. 15A),wherein the first user interface includes: a first visual indicator(e.g., 1402) identifying a payment card associated with multiple paymentaccounts and a second visual indicator (e.g., 1406) identifying a firstpayment account of the multiple payment accounts of the payment card.

At block 1506, the electronic device enables the electronic device touse the first payment account to engage in a payment transaction via theone or more wireless communication elements. At block 1508, theelectronic device detects a first contact on the touch-sensitivesurface.

At block 1510, the electronic device determines whether a characteristicintensity of the first contact is above an intensity threshold.

At block 1512, in accordance with a determination that thecharacteristic intensity of the first contact is above the intensitythreshold (e.g., hard press), the electronic device displays, on thedisplay, a second user interface (e.g., 1418 of FIG. 14D or the userinterface of FIG. 14C), wherein the second user interface enablesselection between different payment accounts represented by the firstvisual indicator.

In accordance with some embodiments, the second user interface includesa payment account selection affordance (e.g., 1412). The electronicdevice detects a second contact at a location on the touch-sensitivesurface corresponding to the payment account selection affordance (e.g.,1412). In response to detecting the second contact, the electronicdevice displays, on the display, a third user interface (e.g., 1418),wherein the third user interface (e.g., 1418) includes one or moreaccount affordances (e.g., 1420, 1422, 1424) corresponding to at leastsome of the multiple payment accounts. The electronic device detects athird contact at a location associated with an account affordance (e.g.,1424) of the one or more account affordances (e.g., 1420, 1422, 1424),wherein the account affordance (e.g., 1424) corresponds to a secondpayment account of the multiple payment accounts and the second paymentaccount is different from the first payment account.

In response to detecting the third contact, the electronic devicedisplays, on the display, a fourth user interface (e.g., the userinterface of FIG. 14E), wherein the fourth user interface includes: thefirst visual indicator (e.g., 1402) identifying the payment cardassociated with multiple payment accounts, and a third visual indicator(e.g., 1430) identifying the second payment account of the multiplepayment accounts of the payment card. In response to detecting the thirdcontact, the electronic device enables the electronic device to use thesecond payment account to engage in a payment transaction via the one ormore wireless communication elements (and disables the electronic devicefrom using the first payment account to engage in a paymenttransaction).

In accordance with some embodiments, in accordance with a determinationthat the characteristic intensity of the first contact is below theintensity threshold (e.g., a light press), the electronic devicemaintains display of the first visual indicator (e.g., 1402) (and,optionally, the second visual indicator 1406) without displaying, on thedisplay, the second user interface.

In accordance with some embodiments, the one or more account affordances(e.g., 1420, 1422, 1424) include a plurality of account affordances.

In accordance with some embodiments, a visual indicator (e.g., 1420,1422, 1424) of a currently selected payment account is highlighted(e.g., different color, displayed with a check mark 1428, etc.) on thesecond user interface.

In accordance with some embodiments, detecting the second contactincludes determining that a characteristic intensity of the secondcontact is not above an intensity threshold (e.g., it is not a hardpress).

In accordance with some embodiments, the second user interface includesa payment account deletion affordance (e.g., 1410). The electronicdevice detects activation of the payment account deletion affordance(e.g., 1410). In response to detecting activation of the payment accountdeletion affordance (e.g., 1410), the electronic device removes (e.g.,unlinks from the electronic device) the multiple payment accounts of thepayment card from an electronic wallet of the device.

In accordance with some embodiments, the payment account deletionaffordance (e.g., 1410) includes one or more visual characteristicsdifferentiating the payment account deletion affordance from the paymentaccount selection affordance (e.g., 1412).

In accordance with some embodiments, while displaying, on the display,the fourth user interface, the electronic device detects a swipe input(e.g., horizontal swipe input) on the touch-sensitive surface. In someembodiments, the swipe input has a characteristic intensity below theintensity threshold. In response to detecting the swipe input, theelectronic device displays a fifth user interface, wherein the fifthuser interface includes a fourth visual indicator identifying a secondpayment card different from the payment card.

In accordance with some embodiments, the first user interface, thesecond user interface, the third user interface, and the fourth userinterface are user interfaces of a single electronic wallet application,the single electronic wallet application including a plurality ofpayment accounts associated with a user of the electronic device.

In accordance with some embodiments, the electronic device receives arequest for account information from a contactless payment terminal. Inresponse to receiving the request for account information, theelectronic device transmits, via the one or more wireless communicationelements, account information for the second payment account to thecontactless payment terminal, wherein the account information enablesthe contactless payment terminal to engage in a payment transaction. Insome embodiments, engaging in the payment transaction includes routinginformation to one or more financial institutions to verify paymentcredentials and/or receive authorization to complete the transaction.For example, the payment account information is transmitted to acontactless payment terminal using NFC.

Note that details of the processes described above with respect tomethod 1500 (e.g., FIG. 15 ) are also applicable in an analogous mannerto the methods described above and below. For example, methods 700, 900,1100, 1300, 1700, and 1900 may include one or more of thecharacteristics of the various methods described above with reference tomethod 1500. For example, the electronic wallet, payment accounts,loyalty accounts, affordances, and inputs of methods 700, 900, 1100,1300, 1700, and 1900 optionally have one or more of the characteristicsof the electronic device, payment accounts, loyalty accounts,affordances, and inputs of the electronic device described in method1500. For brevity, these details are not repeated below.

FIGS. 16A-16G illustrate exemplary techniques and exemplary userinterfaces for linking a payment account to one or more electronicdevices, in accordance with some embodiments. The technique is performedat a first electronic device with a display and one or more wirelesscommunication elements (e.g., one or more wireless antennas such as NFCantennas, WiFi antennas.). The user interfaces in these figures are usedto illustrate the processes described below, including the processes inFIG. 17 .

A user may want to add a payment account to two devices, which arepaired with each other, such as the user's phone and the user's smartwatch. The following description describes a technique for linking thepayment account to the user's first device (e.g., phone) and the user'ssecond device (e.g., smart watch) in a convenient and efficient manner.

At FIG. 16A, the first electronic device displays a user interfaceincluding three affordances for linking a payment account to the firstelectronic device. For example, affordance 1606, when activated, allowsfor importing payment account details from a remote server; affordance1608, when activated, allows for manually entering payment accountdetails (e.g., using a displayed keypad); affordance 1610, whenactivated, allows for capturing payment account details using a camerasensor of the first electronic device.

At FIG. 16B, the first electronic device may display a user interfacethat includes a payment account indication 1612 representing the paymentaccount. The device may prompt the user to enter the security code(e.g., a numerical card security code such as CVD, CVV, CVC) of thepayment account. For example, the device can receive input using keypad1616 for entry of the security code into field 1614. Thus, the firstelectronic device receives a first request (e.g., a user input) to linka payment account associated with a payment card (e.g., a credit card)to the first electronic device.

In response to receiving the first request, the first electronic deviceinitiates a process for linking the payment account to the firstelectronic device. As illustrated in FIG. 16B, in some examples, duringthe process for linking the payment account to the first electronicdevice, the first electronic device receives input of a security code(e.g., a numerical card security code such as CVD, CVV, CVC) of thepayment card. For example, the user may enter the security code intofield 1614 by using keypad 1616. In some examples, the first electronicdevice determines whether further verification is needed to link thepayment account to the first electronic device. In accordance with adetermination that further verification is not needed to link thepayment account to the first electronic device, the first electronicdevice links the payment account to the electronic device. Asillustrated in FIG. 16C, in accordance with a determination that furtherverification is needed to link the payment account to the firstelectronic device, the first electronic device provides an indicationthat further verification is needed to link the payment account to therespective device (e.g., displaying on the display of the firstelectronic device that approval for linking the payment account ispending or requesting the user to call a phone number for verification).In this example, the user can activate affordance 1618 to receive atelephone call to complete the further verification or the user canactivate affordance 1620 to receive an email to complete the furtherverification. In some embodiments, the indication that furtherverification is needed to link the payment account to the firstelectronic device includes an alphanumeric visual indicator displayed onthe display of the electronic device (e.g., the alphanumeric indicatorcomprising “approval pending” that indicates that further verificationsteps have been initiated without additional user input). For example, afinancial institution (e.g., a bank) associated with the payment accountmay need to confirm details of the payment account before the paymentaccount is linked to the respective device. The verification may or maynot require additional user interaction with the financial institution.Additional details regarding the determination and process for furtherverification is described in U.S. Provisional Patent Application Ser.No. 62/004,886, “USER INTERFACE FOR PAYMENTS,” which is herebyincorporated by reference in its entirety.

As illustrated in FIG. 16D, after successfully linking the paymentaccount to the first electronic device (e.g., in response to linking thepayment account to the first electronic device), the first electronicdevice concurrently displays, on the display, an indication 1638 thatthe payment account has been successfully linked to the first electronicdevice and a selectable affordance 1640 for linking the payment accountto a second electronic device different from the first electronicdevice.

The first electronic device receives activation of the selectableaffordance 1640 (e.g., user activates the selectable affordance 1640 bytapping on the affordance). In response to receiving activation of theselectable affordance 1640, the first electronic device initiates aprocess for linking the payment account to the second electronic device(e.g., as illustrated in FIGS. 16E-16F).

In accordance with some embodiments, the second electronic device isuniquely paired with the first electronic device. For example, thesecond electronic device has a special relationship with the firstelectronic device in that the second electronic device is only pairedwith the first electronic device and is not paired with any otherdevices.

In accordance with some embodiments, the first electronic device ispaired with the second electronic device and the first electronic deviceis paired with a third electronic device, and wherein a pairingrelationship between the first electronic device and the secondelectronic device is different than a pairing relationship between thefirst electronic device and the third electronic device.

In accordance with some embodiments, initiating the process for linkingthe payment account to the second electronic device includes (the firstelectronic device) transmitting, via the one or more wirelesscommunication elements, to a financial institution associated with thepayment card an indication that the second electronic device is uniquelypaired with the first electronic device. For example, the firstelectronic device sends a security token to the financial institutionindicating that the second electronic device is uniquely paired with adevice that was just linked to the same payment account.

In accordance with some embodiments, after initiating linking thepayment account to the second electronic device, the first electronicdevice receives a confirmation from the second electronic device thatlinking the second electronic device to the payment account wassuccessful. A primary account number (e.g., Digital PAN, DPAN, a16-digit account number, or other account number, which, for example,cannot be used for completing a manual transaction over a voicecall—only for completing a payment electronically through the device)linked to the second electronic device for the payment account isdifferent from a primary account number (e.g., Digital PAN, DPAN, a16-digit account number, or other account number) linked to the firstelectronic device for the payment account. As illustrated in FIG. 16G,in some examples, the first electronic device displays a confirmation1636 that the payment account was linked to the second electronicdevice.

In accordance with some embodiments, the first request (e.g., a userinput) to link a payment account (to the first electronic device)includes an account number of the payment card (e.g., which is providedby the user through manual entry, imported from a server, or input bythe user via a camera sensor of the electronic device) and whereininitiating the process for linking the payment account to the secondelectronic device occurs without requiring additional input (e.g., userinput) of the account number of the payment card.

As illustrated in FIG. 16F, in accordance with some embodiments, asecond request (e.g., to link the payment account to the secondelectronic device, which initiates the process for linking the paymentaccount to the second electronic device) includes a security code (e.g.,a numerical card security code such as CVD, CVV, CVC) of the paymentcard (e.g., that was input by a user). For example, a user can enter thesecurity code into field 1634 using keypad 1628.

In accordance with some embodiments, the first electronic deviceinitiates the process for linking the payment account to the secondelectronic device.

In accordance with some embodiments, initiating the process linking thepayment account to the second electronic device includes (the firstelectronic device) transmitting, via the one or more wirelesscommunication elements, to a financial institution associated with thepayment card (1) the account number of the credit card and (2) asecurity token confirming the payment account was previously linked tothe first electronic device. In some embodiments, the security token isgenerated by the electronic device after linking the payment account tothe first device. In some embodiments, the security token is received bythe electronic device from the financial institution after linking thepayment account to the first device.

In accordance with some embodiments, initiating the process for linkingthe payment account to the second electronic device includes: (the firstelectronic device) determining whether further verification is needed tolink the payment account to the second electronic device; in accordancewith a determination that further verification is not needed to link thepayment account to the second electronic device, (the first electronicdevice) initiating a process for linking the payment account to thesecond electronic device and providing an indication (e.g., on thedisplay) that the payment account has been linked to the secondelectronic device; and, as illustrated in FIG. 16E, in accordance with adetermination that further verification is needed to link the paymentaccount to the second electronic device, (the first electronic device)providing an indication 1642 (e.g., on the display) that furtherverification is needed to link the payment account to the secondelectronic device.

As illustrated in FIG. 16E, in accordance with some embodiments, theindication that further verification is needed to link the paymentaccount to the second electronic device includes a visual indication ofadditional steps to be taken by a user to link the payment account tothe respective device (e.g., affordance 1630 with phone number to becalled; affordance 1632 with email address to be emailed).

In accordance with some embodiments, the first electronic devicetransmits account linking information to the second electronic device.The account linking information enables the second electronic device tolink the payment account to the second electronic device.

In accordance with some embodiments, in accordance with thedetermination that further verification is needed to link the paymentaccount to the second electronic device, the first electronic devicedisplays, on the display, a plurality of communication methodaffordances, wherein each communication method affordance is associatedwith a respective communication method for a verification communication.The plurality of communication method affordances is based oncommunication received from the financial institution.

In accordance with some embodiments, in accordance with thedetermination that further verification is needed to link the paymentaccount to the second electronic device, the first electronic devicereceives a selection of a communication method affordance of theplurality of communication method affordances, and in response toreceiving the selection of the communication method affordance, thefirst electronic device transmits, to the financial institution, anindication of the respective communication method of the selectedcommunication method affordance. The verification communication is basedon the communication method affordance.

In accordance with some embodiments, the first electronic devicereceives a primary account number from the financial institution for usein authorizing payments from the payment account using the secondelectronic device. The primary account number is different than theaccount number of the credit card. The first electronic device assignsthe primary account number to the second electronic device.

In accordance with some embodiments, an electronic wallet of the secondelectronic device includes payment account information for a secondpayment account associated with a user of the second electronic device,wherein the second payment account is distinct from the payment account.

In accordance with some embodiments, the first electronic devicereceives, from the second electronic device, an indication that thesecond electronic device participated in a payment transaction using thelinked payment account. For example, the second electronic devicetransmits, using the one or more wireless communication elements of thesecond electronic device, payment account information of the linkedpayment account to a contactless payment terminal that is proximate tothe second electronic device, wherein the payment account informationenables the contactless payment terminal to engage in a paymenttransaction; In some embodiments, engaging in the payment transactionincludes routing information to one or more financial institutions toverify payment credentials and/or receive authorization to complete thetransaction. For example, the payment account information is transmittedto a contactless payment terminal using NFC.

FIG. 17 is a flow diagram illustrating a method for linking a paymentaccount to one or more electronic devices, in accordance with someembodiments. Method 1700 is performed at a device (e.g., 100, 300, 500)with a display and one or more wireless communication elements (e.g.,one or more wireless antennas such as NFC antennas, WiFi antennas.).Some operations in method 1700 may be combined, the order of someoperations may be changed, and some operations may be omitted.

As described below, method 1700 provides an intuitive way for linking apayment account to one or more electronic devices, in accordance withsome embodiments. The method reduces the cognitive burden on a user forlinking a payment account to one or more electronic devices, therebycreating a more efficient human-machine interface. For battery-operatedcomputing devices, enabling a user to select an account faster and moreefficiently conserves power and increases the time between batterycharges.

At block 1702, the first electronic device receiving a first request(e.g., a user input) to link a payment account associated with a paymentcard (e.g., a credit card) to the first electronic device.

At block 1704, in response to receiving the first request, the firstelectronic device initiates a process for linking the payment account tothe first electronic device.

At block 1706, after successfully linking the payment account to thefirst electronic device (e.g., in response to linking the paymentaccount to the first electronic device), the first electronic deviceconcurrently displays, on the display: an indication (e.g., 1638) thatthe payment account has been successfully linked to the first electronicdevice and a selectable affordance (e.g., 1640) for linking the paymentaccount to a second electronic device different from the firstelectronic device.

At block 1708, the first electronic device receives activation of theselectable affordance (e.g., 1640).

At block 1710, in response to receiving activation of the selectableaffordance (e.g., 1640), the first electronic device initiates a processfor linking the payment account to the second electronic device.

In accordance with some embodiments, the second electronic device isuniquely paired with the first electronic device.

In accordance with some embodiments, the first electronic device ispaired with the second electronic device and the first electronic deviceis paired with a third electronic device, and wherein a pairingrelationship between the first electronic device and the secondelectronic device is different than a pairing relationship between thefirst electronic device and the third electronic device.

In accordance with some embodiments, initiating the process for linkingthe payment account to the second electronic device includes (the firstelectronic device) transmitting, via the one or more wirelesscommunication elements, to a financial institution associated with thepayment card an indication that the second electronic device is uniquelypaired with the first electronic device.

In accordance with some embodiments, after initiating linking thepayment account to the second electronic device, the first electronicdevice receives a confirmation from the second electronic device thatlinking the second electronic device to the payment account wassuccessful. A primary account number (e.g., Digital PAN, DPAN, a16-digit account number, or other account number, which, for example,cannot be used for completing a manual transaction over a voicecall—only for completing a payment electronically through the device)linked to the second electronic device for the payment account isdifferent from a primary account number (e.g., Digital PAN, DPAN, a16-digit account number, or other account number) linked to the firstelectronic device for the payment account.

In accordance with some embodiments, the first request (e.g., a userinput) to link a payment account (to the first electronic device)includes an account number of the payment card (e.g., which is providedby the user through manual entry, imported from a server, or input bythe user via a camera sensor of the electronic device) and whereininitiating the process for linking the payment account to the secondelectronic device occurs without requiring additional input (e.g., userinput) of the account number of the payment card.

In accordance with some embodiments, a second request includes asecurity code (e.g., a numerical card security code such as CVD, CVV,CVC) of the payment card (e.g., that was input by a user).

In accordance with some embodiments, the first electronic deviceinitiates the process for linking the payment account to the secondelectronic device.

In accordance with some embodiments, initiating the process linking thepayment account to the second electronic device includes (the firstelectronic device) transmitting, via the one or more wirelesscommunication elements, to a financial institution associated with thepayment card (1) the account number of the credit card and (2) asecurity token confirming the payment account was previously linked tothe first electronic device. In some embodiments, the security token isgenerated by the electronic device after linking the payment account tothe first device. In some embodiments, the security token is received bythe electronic device from the financial institution after linking thepayment account to the first device.

In accordance with some embodiments, initiating the process for linkingthe payment account to the second electronic device includes: (the firstelectronic device) determining whether further verification is needed tolink the payment account to the second electronic device; in accordancewith a determination that further verification is not needed to link thepayment account to the second electronic device, (the first electronicdevice) initiating a process for linking the payment account to thesecond electronic device and providing an indication (e.g., on thedisplay) that the payment account has been linked to the secondelectronic device; and in accordance with a determination that furtherverification is needed to link the payment account to the secondelectronic device, (the first electronic device) providing an indication(e.g., 1642) that further verification is needed to link the paymentaccount to the second electronic device.

In accordance with some embodiments, the indication (e.g., 1642) thatfurther verification is needed to link the payment account to the secondelectronic device includes a visual indication of additional steps to betaken by a user to link the payment account to the respective device(e.g., affordance 1630 with phone number to be called; affordance 1632with email address to be emailed).

In accordance with some embodiments, the first electronic devicetransmits account linking information to the second electronic device.The account linking information enables the second electronic device tolink the payment account to the second electronic device.

In accordance with some embodiments, in accordance with thedetermination that further verification is needed to link the paymentaccount to the second electronic device, the first electronic devicedisplays, on the display, a plurality of communication methodaffordances, wherein each communication method affordance is associatedwith a respective communication method for a verification communication.The plurality of communication method affordances is based oncommunication received from the financial institution.

In accordance with some embodiments, in accordance with thedetermination that further verification is needed to link the paymentaccount to the second electronic device, the first electronic devicereceives a selection of a communication method affordance of theplurality of communication method affordances, and in response toreceiving the selection of the communication method affordance, thefirst electronic device transmits, to the financial institution, anindication of the respective communication method of the selectedcommunication method affordance. The verification communication is basedon the communication method affordance.

In accordance with some embodiments, the first electronic devicereceives a primary account number from the financial institution for usein authorizing payments from the payment account using the secondelectronic device. The primary account number is different than theaccount number of the credit card. The first electronic device assignsthe primary account number to the second electronic device.

In accordance with some embodiments, an electronic wallet of the secondelectronic device includes payment account information for a secondpayment account associated with a user of the second electronic device,wherein the second payment account is distinct from the payment account.

In accordance with some embodiments, the first electronic devicereceives, from the second electronic device, an indication that thesecond electronic device participated in a payment transaction using thelinked payment account. For example, the second electronic devicetransmits, using the one or more wireless communication elements of thesecond electronic device, payment account information of the linkedpayment account to a contactless payment terminal that is proximate tothe second electronic device, wherein the payment account informationenables the contactless payment terminal to engage in a paymenttransaction; In some embodiments, engaging in the payment transactionincludes routing information to one or more financial institutions toverify payment credentials and/or receive authorization to complete thetransaction. For example, the payment account information is transmittedto a contactless payment terminal using NFC.

Note that details of the processes described above with respect tomethod 1700 (e.g., FIG. 17 ) are also applicable in an analogous mannerto the methods described above and below. For example, methods 700, 900,1100, 1300, 1500, and 1900 may include one or more of thecharacteristics of the various methods described above with reference tomethod 1700. For example, the electronic wallet, payment accounts,loyalty accounts, affordances, and inputs of methods 700, 900, 1100,1300, 1500, and 1900 optionally have one or more of the characteristicsof the electronic device, payment accounts, loyalty accounts,affordances, and inputs of the electronic device described in method1700. For brevity, these details are not repeated below.

FIGS. 18A-18C illustrate exemplary techniques and exemplary userinterfaces for linking a payment account to an electronic device, inaccordance with some embodiments. The technique is performed at a firstelectronic device with a display and one or more wireless communicationelements (e.g., one or more wireless antennas such as NFC antennas, WiFiantennas.). The user interfaces in these figures are used to illustratethe processes described below, including the processes in FIG. 19 .

The first electronic device displays, on the display, a payment-accountuser interface 1800 for a second electronic device (e.g., a smart watch)that is associated with the first electronic device (e.g., the firstelectronic device and the second electronic device are paired, uniquelypaired, signed into the same user account, or linked in some other waythat indicates that the devices share a same user that is associatedwith the payment accounts), wherein displaying the payment-account userinterface 1800 includes concurrently displaying: a representation 1804of a first payment account along with status information 1802 for thefirst payment account indicating that the first payment account islinked to the second electronic device and that the second electronicdevice is configured to enable payment using the first payment account;and a representation 1808 of a second payment account along with statusinformation 1806 for the second payment account indicating that thesecond payment account is linked to the first electronic device but isnot linked to the second electronic device.

In accordance with some embodiments, the status information (e.g., 1802)for the first payment account further indicates that the first paymentaccount is linked to the first electronic device. In accordance withsome embodiments, the status information (e.g., 1802) for the firstpayment account further indicates that the first payment account is notlinked to the first electronic device.

In accordance with some embodiments, the payment-account user interface(e.g., 1800) includes representations (e.g., 1814) of one or moreaccounts that are associated with a user of the electronic device andthat are not linked to the first electronic device and that are notlinked to the second electronic device (e.g., cards on file with anotherapplication, such as Safari autocomplete, or an iTunes account that islinked to the user of the devices). For example, the user can activate arespective representation (e.g., 1816 or 1818) of the one or moreaccounts to initiate a process for linking the corresponding paymentaccount to the first electronic device (e.g., using affordance 1818) orto the second electronic device (e.g., using affordance 1816).

In accordance with some embodiments, the payment-account user interface1800 includes a linking affordance (e.g., 1810) associated with thesecond payment account. For example, the linking affordance (e.g., 1810)indicates that the user's phone (the first electronic device) isprovisioned to make payments using the second payment account, while theuser's watch (the second electronic device) is not provisioned to makepayments using the second payment account. The first electronic devicedetects activation of the linking affordance (e.g. 1810). In response todetecting activation of the linking affordance (e.g., 1810), the firstelectronic device displays, on the display, a user interface (e.g.,1830) for linking the second payment account to the second electronicdevice including a synchronization option (e.g., 1838) to synchronizepayment notifications between the first electronic device and the secondelectronic device. The first electronic device detects activation of thesynchronization option (e.g., user flips the option to ON). In responseto detecting activation of the synchronization option, the firstelectronic device synchronizes future payment notifications to bepresented at both the first electronic device and the second electronicdevice (e.g., visual, audio, or haptic notifications).

In accordance with some embodiments, as illustrated in FIG. 18C, thefirst electronic device receives confirmation that the second paymentaccount is linked to the second electronic device. In response toreceiving the confirmation that the second payment account is linked tothe second electronic device, the first electronic device displays, onthe display, a confirmation 1840 that the second payment account islinked to the second electronic device.

In accordance with some embodiments, displaying the payment-account userinterface 1800 includes concurrently displaying: a first group of afirst plurality of representations of payment accounts that are linkedto the second electronic device and not linked to the first electronicdevice; and a second group of a second plurality of representations ofpayment accounts that are linked to the first electronic device and notlinked to the second electronic device.

In accordance with some embodiments, the payment-account user interface(e.g., 1800) includes a linking affordance (e.g., 1810) associated withthe second payment account. For example, the linking affordance (e.g.,1810) indicates that the user's phone (the first electronic device) isprovisioned to make payments using the payment account, while the user'swatch (the second electronic device) is not provisioned to make paymentsusing the payment account. The first electronic device detectsactivation of the linking affordance (e.g., 1810). In response todetecting activation of the linking affordance (e.g., 1810), the firstelectronic device displays, on the display, a user interface (e.g.,1830) for linking the second payment account to the second electronicdevice. While displaying, on the display, the user interface for linkingthe second payment account to the second electronic device, the firstelectronic device receives a request (e.g., from the user) to initiatelinking the second payment account to the second electronic device,wherein the request to initiate linking the second payment account tothe second electronic device does not include an input (e.g., a userinput) of an account number of the second payment account.

In accordance with some embodiments, the payment-account user interface(e.g., 1800) includes a second linking affordance (e.g., 1822)associated with the first payment account, and wherein the first paymentaccount is not linked to the first electronic device. The firstelectronic device detects activation of the second linking affordance(e.g., 1822). In response to detecting activation of the second linkingaffordance, the first electronic device displays, on the display, a userinterface for linking the first payment account to the first electronicdevice. While displaying, on the display, the user interface for linkingthe first payment account to the first electronic device, the electronicdevice receives a request (e.g., from the user) to initiate linking thefirst payment account to the first electronic device, wherein therequest to initiate linking the first payment account to the firstelectronic device does not include an input (e.g., a user input) of anaccount number of the first payment account.

In accordance with some embodiments, the first electronic device is ahandheld device (e.g., a smart phone) and the second electronic deviceis a wearable device (e.g., a smart watch).

In accordance with some embodiments, the first electronic device is ahandheld device and the second electronic device a personal computingdevice that is larger than the first electronic device (e.g., a tabletor portable laptop computer).

In accordance with some embodiments, the payment-account user interface1800 for the second electronic device that is associated with the firstelectronic device (e.g., the first electronic device and the secondelectronic device are paired, uniquely paired, signed into the same useraccount, or linked in some other way that indicates that the devicesshare a same user that is associated with the payment accounts) furtherincludes: a representation of a third payment account along with statusinformation for the third payment account indicating that the thirdpayment account is linked to a third electronic device and that thethird electronic device is configured to enable payment using the thirdpayment account. The third electronic device is different from the firstelectronic device and the second electronic device (e.g., anotherelectronic device, such as a table, that is associated with the user ofthe first electronic device).

FIG. 19 is a flow diagram illustrating a method for linking a paymentaccount to an electronic device, in accordance with some embodiments.Method 1900 is performed at a device (e.g., 100, 300, 500) with adisplay and one or more wireless communication elements (e.g., one ormore wireless antennas such as NFC antennas, WiFi antennas.). Someoperations in method 1900 may be combined, the order of some operationsmay be changed, and some operations may be omitted.

As described below, method 1900 provides an intuitive way for linking apayment account to an electronic device. The method reduces thecognitive burden on a user for linking a payment account to anelectronic device, thereby creating a more efficient human-machineinterface. For battery-operated computing devices, enabling a user tolinking a payment account to an electronic device faster and moreefficiently conserves power and increases the time between batterycharges.

At block 1902, the first electronic device displays, on the display, apayment-account user interface (e.g., 1800) for a second electronicdevice that is associated with the first electronic device.

At block 1904, displaying the payment-account user interface includesconcurrently displaying, at block 1906, a representation (e.g., 1804) ofa first payment account along with status information (e.g., 1802) forthe first payment account indicating that the first payment account islinked to the second electronic device and that the second electronicdevice is configured to enable payment using the first payment account,and at block 1908, a representation (e.g., 1808) of a second paymentaccount along with status information (e.g., 1806) for the secondpayment account indicating that the second payment account is linked tothe first electronic device but is not linked to the second electronicdevice.

In accordance with some embodiments, the status information (e.g., 1802)for the first payment account further indicates that the first paymentaccount is linked to the first electronic device. In accordance withsome embodiments, the status information (e.g., 1802) for the firstpayment account further indicates that the first payment account is notlinked to the first electronic device.

In accordance with some embodiments, the payment-account user interface(e.g., 1800) includes representations (e.g., 1814) of one or moreaccounts that are associated with a user of the electronic device andthat are not linked to the first electronic device and that are notlinked to the second electronic device (e.g., cards on file with anotherapplication, such as Safari autocomplete, or an iTunes account that islinked to the user of the devices).

In accordance with some embodiments, the payment-account user interface(e.g., 1800) includes a linking affordance (e.g., 1810) associated withthe second payment account. For example, the linking affordance (e.g.,1810) indicates that the user's phone (the first electronic device) isprovisioned to make payments using the second payment account, while theuser's watch (the second electronic device) is not provisioned to makepayments using the second payment account. The first electronic devicedetects activation of the linking affordance (e.g., 1810). In responseto detecting activation of the linking affordance (e.g., 1810), thefirst electronic device displays, on the display, a user interface(e.g., 1830) for linking the second payment account to the secondelectronic device including a synchronization option (e.g., 1838) tosynchronize payment notifications between the first electronic deviceand the second electronic device. The first electronic device detectsactivation of the synchronization option (e.g., user flips the option toON). In response to detecting activation of the synchronization option,the first electronic device synchronizes future payment notifications tobe presented at both the first electronic device and the secondelectronic device (e.g., visual, audio, or haptic notifications).

In accordance with some embodiments, the first electronic devicereceives confirmation that the second payment account is linked to thesecond electronic device. In response to receiving the confirmation thatthe second payment account is linked to the second electronic device,the first electronic device displays, on the display, a confirmation(e.g., 1840) that the second payment account is linked to the secondelectronic device.

In accordance with some embodiments, displaying the payment-account userinterface (e.g., 1800) includes concurrently displaying: a first groupof a first plurality of representations of payment accounts that arelinked to the second electronic device and not linked to the firstelectronic device; and a second group of a second plurality ofrepresentations of payment accounts that are linked to the firstelectronic device and not linked to the second electronic device.

In accordance with some embodiments, the payment-account user interface(e.g., 1800) includes a linking affordance (e.g., 1810) associated withthe second payment account. For example, the linking affordance (e.g.,1810) indicates that the user's phone (the first electronic device) isprovisioned to make payments using the payment account, while the user'swatch (the second electronic device) is not provisioned to make paymentsusing the payment account. The first electronic device detectsactivation of the linking affordance (e.g., 1810). In response todetecting activation of the linking affordance (e.g., 1810), the firstelectronic device displays, on the display, a user interface (e.g.,1830) for linking the second payment account to the second electronicdevice. While displaying, on the display, the user interface for linkingthe second payment account to the second electronic device, the firstelectronic device receives a request (e.g., from the user) to initiatelinking the second payment account to the second electronic device,wherein the request to initiate linking the second payment account tothe second electronic device does not include an input (e.g., a userinput) of an account number of the second payment account.

In accordance with some embodiments, the payment-account user interface(e.g., 1800) includes a second linking affordance (e.g., 1822)associated with the first payment account, and wherein the first paymentaccount is not linked to the first electronic device. The firstelectronic device detects activation of the second linking affordance(e.g., 1822). In response to detecting activation of the second linkingaffordance, the first electronic device displays, on the display, a userinterface for linking the first payment account to the first electronicdevice. While displaying, on the display, the user interface for linkingthe first payment account to the first electronic device, the electronicdevice receives a request (e.g., from the user) to initiate linking thefirst payment account to the first electronic device, wherein therequest to initiate linking the first payment account to the firstelectronic device does not include an input (e.g., a user input) of anaccount number of the first payment account.

In accordance with some embodiments, the first electronic device is ahandheld device (e.g., a smart phone) and the second electronic deviceis a wearable device (e.g., a smart watch).

In accordance with some embodiments, the first electronic device is ahandheld device and the second electronic device a personal computingdevice that is larger than the first electronic device (e.g., a tabletor portable laptop computer).

In accordance with some embodiments, the payment-account user interface(e.g., 1800) for the second electronic device that is associated withthe first electronic device (e.g., the first electronic device and thesecond electronic device are paired, uniquely paired, signed into thesame user account, or linked in some other way that indicates that thedevices share a same user that is associated with the payment accounts)further includes: a representation of a third payment account along withstatus information for the third payment account indicating that thethird payment account is linked to a third electronic device and thatthe third electronic device is configured to enable payment using thethird payment account. The third electronic device is different from thefirst electronic device and the second electronic device (e.g., anotherelectronic device, such as a table, that is associated with the user ofthe first electronic device).

Note that details of the processes described above with respect tomethod 1900 (e.g., FIG. 19 ) are also applicable in an analogous mannerto the methods described above and below. For example, methods 700, 900,1100, 1300, 1500, and 1700 may include one or more of thecharacteristics of the various methods described above with reference tomethod 1900. For example, the electronic wallet, payment accounts,loyalty accounts, affordances, and inputs of methods 700, 900, 1100,1300, 1500, and 1700 optionally have one or more of the characteristicsof the electronic device, payment accounts, loyalty accounts,affordances, and inputs of the electronic device described in method1900. For brevity, these details are not repeated below.

In accordance with some embodiments, FIG. 20 shows an exemplaryfunctional block diagram of an electronic device 2000 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2000 are configured to perform the techniques described above.The functional blocks of the device 2000 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 20 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 20 , an electronic device 2000 includes: a display unit2002, a touch-sensitive surface unit 2004, one or more wirelesscommunication units 2006 including one or more wireless communicationelements, and a processing unit 2008 coupled to the display unit 2002,the touch-sensitive surface unit 2004, and the one or more wirelesscommunication unit 2006.

The processing unit 2008 is configured to: receive (e.g., with receivingunit 2012) an input requesting to enable the device for a paymenttransaction; in response to receiving the input requesting to enable thedevice for a payment transaction: enable display (e.g. with displayenabling unit 2010), on the display unit 2002, of a first visualindicator identifying a first account; and enable (e.g., with enablingunit 2014) the electronic device to participate in a transaction usingthe first account via the one or more wireless communication units 2006;receive (e.g., with receiving unit 2012) one or more swipe inputs in afirst direction via the touch-sensitive surface unit 2004; in responseto receiving the one or more user swipe inputs: enable display (e.g.with display enabling unit 2010), on the display unit 2002, of a secondvisual indicator identifying a second account; and enable (e.g., withenabling unit 2014) the electronic device to participate in atransaction using the second account via the one or more wirelesscommunication units 2006; and wherein the first visual indicator isdifferent from the second visual indicator.

In some embodiments, the first account is a payment account and thesecond account is a loyalty account.

In some embodiments, the first account is a payment account and thesecond account is a payment account.

In some embodiments, the processing unit 2008 is further configured to:while displaying the second visual indicator: receive (e.g., withreceiving unit 2012) a card code display input; and in response toreceiving the card code display input, enable display (e.g. with displayenabling unit 2010), on the display unit 2002, of visual loyalty cardcode information.

In some embodiments, the processing unit 2008 is further configured to:while displaying the second visual indicator: receive (e.g., withreceiving unit 2012) a request for account information from acontactless payment terminal; and in response to receiving the requestfor account information, transmit (e.g., with transmitting unit 2016),via the one or more wireless communication units 2006, accountinformation for the second account to the contactless payment terminal,wherein the account information enables the contactless payment terminalto engage in the payment transaction.

In some embodiments, the processing unit 2008 is further configured to:while displaying the second visual indicator and after transmittingaccount information for the second account to the contactless paymentterminal: receive (e.g., with receiving unit 2012), via the one or morewireless communication units 2006, a failure communication from thecontactless payment terminal; and in response to receiving the failurecommunication: enable display (e.g. with display enabling unit 2010), onthe display unit 2002, of an indication that the second account was notaccepted; and provide an option to enable the electronic device toparticipate in the transaction using an account different from thesecond account.

In some embodiments, the processing unit 2008 is further configured to:subsequent to transmitting account information for the second account tothe contactless payment terminal, enable concurrent display (e.g., withdisplay enabling unit 2010), on the display unit 2002, of an indicationthat the first account and the second account were both used during thepayment transaction.

In some embodiments, enabling the electronic device to participate inthe transaction using the second account via the one or more wirelesscommunication units 2006 does not require receiving a second user inputrequesting to enable the device for a payment transaction.

In some embodiments, enabling the electronic device to participate inthe transaction using the first account includes displaying a firstanimation of a ready indicator appearing from under an image of a cardof the first account, wherein the ready indicator indicates that thedevice is enabled to participate in payment transactions using the firstaccount. The processing unit 2008 is further configured to: in responseto receiving a portion of the one or more user swipe inputs, enabledisplay (e.g. with display enabling unit 2010), on the display unit2002, of a second animation of the ready indicator to slide the readyindicator back under the image of the card of the first account.

In some embodiments, enabling display, on the display unit 2002, of thefirst visual indicator identifying the first account occurs prior toenabling the electronic device to participate in the transaction usingthe first account via the one or more wireless communication units 2006;and enabling display, on the display unit 2002, of the second visualindicator identifying the second account occurs prior to enabling theelectronic device to participate in the transaction using the secondaccount via the one or more wireless communication units 2006.

In some embodiments, one of the first account and the second account isa payment account and one of the first account and the second account isa loyalty account; and the first visual indicator of the first accounthas a first dimension characteristic; and the second visual indicator ofthe second account has a second dimension characteristic different fromthe first dimension characteristic.

In some embodiments, an electronic wallet of the electronic deviceincludes payment account information for a plurality of payment accountsassociated with a user of the electronic device.

The operations described above with reference to FIG. 7 are, optionally,implemented by components depicted in FIGS. 1A-1B, FIG. 5B, or FIG. 20 .For example, receiving operation 702, displaying operation 706, andenabling operation 708 may be implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIG.1A-1B or 5B.

In accordance with some embodiments, FIG. 21 shows an exemplaryfunctional block diagram of an electronic device 2100 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2100 are configured to perform the techniques described above.The functional blocks of the device 2100 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 21 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 21 , an electronic device 2100 includes: a display unit2102, a location sensor unit 2104, and a processing unit 2106 coupled tothe display unit 2102 and a location sensor unit 2104.

The processing unit 2106 is configured to: detect (e.g., with detectingunit 2110), using the location sensor unit 2104, a current location;determine (e.g., with determining unit 2112) whether the currentlocation is associated with a first account; in accordance with afailure to determine that the current location is associated with anaccount other than a default payment account, enable display (e.g., withdisplay enabling unit 2108), on the display unit 2102, of a visualindication of a default payment account; in accordance with adetermination that the current location is associated with the firstaccount, enable concurrent display (e.g., with display enabling unit2108), on the display unit 2102, of the visual indication of the defaultpayment account and a visual indication of the first account; andwherein the default payment account and the first account are linked tothe electronic device and the default payment account and the firstaccount are different.

In some embodiments, the first account is a payment account. In someembodiments, the first account is a loyalty account.

In some embodiments, the processing unit 2106 is further configure to:receive (e.g., with receiving unit 2114) a request associated with apayment transaction from a contactless payment terminal; determine(e.g., with determining unit 2112) whether the request includes arequest for payment account information using a first account typecorresponding to the first account; and in accordance with thedetermination that the current location is associated with the firstaccount and in accordance with a determination that the request includesa request for payment information using the first account type, transmit(e.g., with transmitting unit 2116), using one or more wirelesscommunication elements, payment account information of the first accountto the contactless payment terminal, wherein the payment accountinformation of the first account enables the contactless paymentterminal to engage in the payment transaction.

In some embodiments, the processing unit 2106 is further configure to:receive (e.g., with receiving unit 2114) a request associated with apayment transaction from a contactless payment terminal; determine(e.g., with determining unit 2112) that the request includes a requestfor payment account information using a first account type correspondingto the first account; and in accordance with the failure to determinethat the current location is associated with an account other than thedefault payment account, transmit (e.g., with transmitting unit 2116),using one or more wireless communication elements, payment accountinformation of the default payment account to the contactless paymentterminal, wherein the payment account information of the default paymentaccount enables the contactless payment terminal to engage in thepayment transaction.

In some embodiments, the visual indication of the first account isdisplayed on the visual indication of the default account, and whereinthe visual indication of the first account indicates that the firstaccount is enabled to be selected by the device for use in a paymenttransaction without requiring additional user input.

In some embodiments, the processing unit 2106 is further configure to:prior to detecting, using the location sensor unit 2104, the currentlocation, receive (e.g., with receiving unit 2114) an input requestingto enable the device for a payment transaction.

In some embodiments, detecting, using the location sensor unit 2104, thecurrent location is in response to receiving the input requesting toenable the device for a payment transaction.

In some embodiments, determining whether the current location isassociated with the first account is in response to receiving an inputrequesting to enable the device for a payment transaction.

In some embodiments, a failure to determine that the current location isassociated with an account other than a default payment account occurswhen the device fails to determine that the current location isassociated with a first account before the electronic device is enabledto participate in a transaction using the default payment account viaone or more wireless communication elements.

In some embodiments, the processing unit 2106 is further configure to:receive (e.g., with receiving unit 2114) a request for loyalty accountinformation from a contactless payment terminal, wherein the firstaccount is a loyalty account; and in response to receiving the requestfor loyalty account information, in accordance with the failure todetermine that the current location is associated with an account otherthan the default payment account and in accordance with a subsequentdetermination that the current location is associated with the firstaccount: transmit (e.g., with transmitting unit 2116), via one or morewireless communication elements, account information for the firstaccount to the contactless payment terminal; and transmit (e.g., withtransmitting unit 2116), via the one or more wireless communicationelements, payment account information of the default payment account tothe contactless payment terminal.

In some embodiments, the processing unit 2106 is further configure to:receive (e.g., with receiving unit 2114) a request associated with apayment transaction from a contactless payment terminal; determine(e.g., with determining unit 2112) that the request includes a requestfor payment account information using a first account type correspondingto the first account, wherein the first account is a payment accountthat is different from the default payment account; in response toreceiving the request for account information in accordance with thefailure to determine that the current location is associated with anaccount other than the default payment account and in accordance with asubsequent determination that the current location is associated withthe first account: forgo transmitting (e.g., with transmitting unit2116), via one or more wireless communication elements, accountinformation for the first account to the contactless payment terminal;and transmit (e.g., with transmitting unit 2116), via the one or morewireless communication elements, payment account information of thedefault payment account to the contactless payment terminal.

In some embodiments, the processing unit 2106 is further configure to:receive (e.g., with receiving unit 2114) a request associated with apayment transaction from a contactless payment terminal, wherein: priorto receiving the request associated with the payment transaction fromthe contactless payment terminal, the visual indication of the defaultpayment account and the visual indication of the first account wereconcurrently displayed, on the display unit 2102; wherein the requestincludes a request for payment account information using a first accounttype corresponding to the first account; and wherein the first accountis a payment account of the first account type; and in response toreceiving the request for account information and in accordance with thefailure to determine that the current location is associated with anaccount other than the default payment account and in accordance with asubsequent determination that the current location is associated withthe first account: forgo transmitting (e.g., with transmitting unit2116), via one or more wireless communication elements, accountinformation for the default payment account to the contactless paymentterminal; and transmit (e.g., with transmitting unit 2116), via the oneor more wireless communication elements, payment account information ofthe first account to the contactless payment terminal.

In some embodiments, the processing unit 2106 is further configure to:in accordance with the determination that the current location isassociated with the first account: receive (e.g., with receiving unit2114), via the one or more wireless communication elements, a failurecommunication from the contactless payment terminal; and in response toreceiving the failure communication: transmit (e.g., with transmittingunit 2116), via one or more wireless communication elements, accountinformation for the default payment account to the contactless paymentterminal.

In some embodiments, enabling concurrent display, on the display unit2102, of the visual indication of the default payment account and avisual indication of the first account includes enabling concurrentdisplay, on the display unit 2102, of the visual indication of thedefault payment account in a stack with the visual indication of thefirst account.

The operations described above with reference to FIG. 9 are, optionally,implemented by components depicted in FIGS. 1A-1B, FIG. 5B, or FIG. 21 .For example, detecting operation 902, determining operation 904, anddisplaying operation 906 may be implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIG.1A-1B or 5B.

In accordance with some embodiments, FIG. 22 shows an exemplaryfunctional block diagram of an electronic device 2200 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2200 are configured to perform the techniques described above.The functional blocks of the device 2200 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 22 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 22 , an electronic device 2200 includes: a display unit2202, and, optionally, a touch-sensitive surface unit 2204, a locationsensor unit 2206, and one or more wireless communication unit 2208. Theelectronic device 2200 also includes a processing unit 2210 coupled tothe display unit 2202, and, optionally, to the touch-sensitive surfaceunit 2204, the location sensor unit 2206, and the one or more wirelesscommunication unit 2208.

The processing unit 2210 is configured to: receive (e.g., with receivingunit 2216) an input requesting to enable the device for a paymenttransaction; and in response to receiving the input: detect (e.g., withdetecting unit 2222), using the location sensor unit 2206, a currentlocation; determine (e.g., with determining unit 2214) whether a set ofone or more payment criteria have been met, wherein the set of one ormore payment criteria includes a criterion that is met when the currentlocation is associated with a first payment account; in accordance witha determination that the set of one or more payment criteria is not met,enable display (e.g., with display enabling unit 2212), on the displayunit 2202, of a visual indication of a default payment account, whereinthe default payment account is different from the first payment account;and in accordance with a determination that the set of one or morepayment criteria is met, enable display (e.g., with display enablingunit 2212), on the display unit 2202, of a visual indication of thefirst payment account.

In some embodiments, the processing unit 2210 is further configured to:in accordance with the determination that the set of one or more paymentcriteria is met, enable (e.g., with enabling unit 2218) the electronicdevice to participate in a transaction using the first payment accountvia the one or more wireless communication unit 2208.

In some embodiments, the processing unit 2210 is further configured to:in accordance with the determination that the set of one or more paymentcriteria is not met, enable the electronic device to participate in atransaction using the default payment account via the one or morewireless communication unit 2208.

In some embodiments, the processing unit 2210 is further configured to:in accordance with the determination that the set of one or more paymentcriteria is not met, forgo enabling display (e.g., with display enablingunit 2212), on the display unit 2202, of the visual indication of thefirst payment account.

In some embodiments, the processing unit 2210 is further configured to:receive (e.g., with receiving unit 2216) one or more inputs in a firstdirection; in response to receiving the one or more inputs: enabledisplay (e.g., with display enabling unit 2212), on the display unit2202, of a second visual indicator identifying a second accountdifferent from the first payment account and the default paymentaccount; and enable (e.g., with enabling unit 2218) the electronicdevice to participate in a transaction using the second account via theone or more wireless communication elements.

In some embodiments, the processing unit 2210 is further configured to:receive a request for account information from a contactless paymentterminal; and in response to receiving a request for accountinformation, transmit (e.g., with transmitting unit 2220), via the oneor more wireless communication units 2208, account information for arespective enabled account to the contactless payment terminal, whereinthe account information enables the contactless payment terminal toengage in the payment transaction.

In some embodiments, the set of one or more criteria includes acriterion that is met when the device is authorized to use the firstpayment account for transactions at the current location.

In some embodiments, the processing unit 2210 is further configured to:determine (e.g., with determining unit 2214) that the current locationis associated with a loyalty account; and enable concurrent display(e.g., with display enabling unit 2212), on the display unit 2202, of avisual indication of the loyalty account along with a respective visualindication of a payment account.

In some embodiments, the processing unit 2210 is further configured to:prior to receiving the user input requesting to enable the device for apayment transaction: receive (e.g., with receiving unit 2216) a requestto link a payment account with the electronic device, the requestcomprising account information of the payment account; link (e.g., withlinking unit 2222) the payment account with the electronic device;determine (e.g., with determining unit 2214) that a financialinstitution associated with the payment account has authorized thepayment account for selection based on location without requiring userinput; and receive (e.g., with receiving unit 2216) user inputactivating the payment account for selection based on location withoutrequiring user input.

In some embodiments, the processing unit 2210 is further configured to:in accordance with the determination that the set of one or more paymentcriteria is met, enable (e.g., with enabling unit 2218) the electronicdevice to participate in a transaction using the first payment accountvia the one or more wireless communication elements; receive (e.g., withreceiving unit 2216) a request associated with a payment transactionfrom a contactless payment terminal; determine (e.g., with determiningunit 2214) whether the request includes a request for payment accountinformation using an account type corresponding to a second paymentaccount different from the first payment account; and in accordance witha determination that the request includes a request for paymentinformation using the second account type, provide (e.g., with providingunit 2224) a notification requesting authorization to transmit, usingone or more wireless communication elements, payment account informationof the second account to the contactless payment terminal, wherein thepayment account information of the second account enables thecontactless payment terminal to engage in the payment transaction.

The operations described above with reference to FIG. 11 are,optionally, implemented by components depicted in FIGS. 1A-1B, FIG. 5B,or FIG. 22 . For example, receiving operation 1102, detecting operation1106, and determining operation 1108 may be implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIG.1A-1B or 5B.

In accordance with some embodiments, FIG. 23 shows an exemplaryfunctional block diagram of an electronic device 2300 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2300 are configured to perform the techniques described above.The functional blocks of the device 2300 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 23 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 23 , an electronic device 2300 includes: a display unit2302, one or more wireless communication unit 2304, and a processingunit 2306 coupled to the display unit 2302 and to the one or morewireless communication unit 2304.

The processing unit 2306 is configured to: receive (e.g., with receivingunit 2310) an input requesting to enable the device for a paymenttransaction; in response to receiving the input, enable display (e.g.,with display enabling unit 2308), on the display unit 2302, of a paymentindication that represents a plurality of payment accounts including afirst payment account and a second payment account; receive (e.g., withreceiving unit 2310), via the one or more wireless communication unit2304, a request for account information corresponding to a paymenttransaction; in response to receiving the request for accountinformation corresponding to the payment transaction: in accordance witha determination that payment criteria for a first payment account havebeen met, transmit (e.g., with transmitting unit 2314), via the one ormore wireless communication unit 2304, account information for the firstpayment account without transmitting account information for the secondpayment account; and in accordance with a determination that paymentcriteria for the second payment account have been met, transmit (e.g.,with transmitting unit 2314), via the one or more wireless communicationunit 2304, account information for the second payment account withouttransmitting account information for the first payment account.

In some embodiments, the electronic device is configured to enablepayment using one of a default payment account and a plurality ofnon-default payment accounts. The processing unit 2306 is furtherconfigured to: in accordance with a determination that payment criteriahave not been met for any of the non-default payment accounts, transmit(e.g., with transmitting unit 1214), via the one or more wirelesscommunication unit 2304, account information for the default paymentaccount without transmitting account information for the non-defaultpayment accounts.

In some embodiments, the payment criteria include a criterion based on adetermination associated with a current location of the electronicdevice. In some embodiments, the payment criteria include a criterionbased on the request for account information corresponding to thepayment transaction.

In some embodiments, the payment indication that represents theplurality of payment accounts does not include an indication of thefirst payment account and does not include an indication of the secondpayment account.

In some embodiments, the plurality of payment accounts only includepayment accounts for which the electronic device has received user inputactivating selection based on location without requiring user input.

In some embodiments, the plurality of payment accounts only includepayment accounts for which a financial institution associated with thepayment account has authorized the respective payment account forselection based on location without requiring user input.

In some embodiments, a contextual-selection mode of operation in whichthe device selects, based on context, which of the plurality of paymentaccounts to use for a payment transaction is represented as a selectablepayment option.

In some embodiments, the electronic device optionally includes atouch-sensitive surface unit. The processing unit 2306 is furtherconfigured to: receive (e.g., with receiving unit 2310) one or moreinputs in a first direction; in response to receiving the one or moreinputs: enable replacement of the display (e.g., with display enablingunit 2308), on the display unit 2302, of the payment indication thatrepresents the plurality of payment accounts with a second visualindicator different from the payment indication that represents theplurality of payment accounts, wherein the second visual selectionindicator identifies a third payment account different from the firstpayment account and the second payment account; and enable (e.g., withenabling unit 2312) the electronic device to participate in atransaction using the third payment account via the one or more wirelesscommunication elements.

In some embodiments, the payment indication that represents theplurality of payment accounts is different from the visual indicators ofindividual payment accounts of the plurality of payment accounts.

The operations described above with reference to FIG. 13 are,optionally, implemented by components depicted in FIGS. 1A-1B, FIG. 5B,or FIG. 23 . For example, receiving operation 1302, displaying operation1306, and receiving operation 1308 may be implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIG.1A-1B or 5B.

In accordance with some embodiments, FIG. 24 shows an exemplaryfunctional block diagram of an electronic device 2400 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2400 are configured to perform the techniques described above.The functional blocks of the device 2400 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 24 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 24 , an electronic device 2400 includes: a display unit2402, a touch-sensitive surface unit 2404, one or more wirelesscommunication unit 2406, and a processing unit 2408 coupled to thedisplay unit 2402, the touch-sensitive surface unit 2404 configured todetect intensity of contacts, and the one or more wireless communicationunit 2406.

The processing unit 2408 is configured to: receive (e.g., with receivingunit 2420) a first input; in response to receiving the first input:enable display (e.g., with display enabling unit 2410), on the displayunit 2402, of a first user interface, wherein the first user interfaceincludes: a first visual indicator identifying a payment card associatedwith multiple payment accounts, and a second visual indicatoridentifying a first payment account of the multiple payment accounts ofthe payment card; enable (e.g., with enabling unit 2422) the electronicdevice to use the first payment account to engage in a paymenttransaction via the one or more wireless communication elements; detect(e.g., with detecting unit 2412) a first contact on the touch-sensitivesurface unit; determine (e.g., with determining unit 2414) whether acharacteristic intensity of the first contact is above an intensitythreshold; and in accordance with a determination that thecharacteristic intensity of the first contact is above the intensitythreshold, enable display (e.g., with display enabling unit 2410), onthe display unit 2402, of a second user interface, wherein the seconduser interface enables selection between different payment accountsrepresented by the first visual indicator.

In some embodiments, the second user interface includes a paymentaccount selection affordance, and the processing unit 2408 is furtherconfigured to: detect (e.g., with detecting unit 1412) a second contactat a location on the touch-sensitive surface unit corresponding to thepayment account selection affordance; and in response to detecting thesecond contact, enable display (e.g., with display enabling unit 2410),on the display unit 2402, of a third user interface, wherein the thirduser interface includes one or more account affordances corresponding toat least some of the multiple payment accounts; detect (e.g., withdetecting unit 2412) a third contact at a location on thetouch-sensitive surface unit associated with an account affordance ofthe one or more account affordances, wherein the account affordancecorresponds to a second payment account of the multiple payment accountsand the second payment account is different from the first paymentaccount; and in response to detecting the third contact: enable display(e.g., with display enabling unit 2410), on the display unit 2402, of afourth user interface, wherein the fourth user interface includes: thefirst visual indicator identifying the payment card associated withmultiple payment accounts, and a third visual indicator identifying thesecond payment account of the multiple payment accounts of the paymentcard; enable (e.g., with enabling unit 2422) the electronic device touse the second payment account to engage in a payment transaction viathe one or more wireless communication elements.

In some embodiments, the second user interface includes one or moreaccount affordances corresponding to at least some of the multiplepayment accounts, and the processing unit 2408 is further configured to:detect (e.g., with detecting unit 2412) a second contact at a locationon the touch-sensitive surface unit associated with an accountaffordance of the one or more account affordances, wherein the accountaffordance corresponds to a second payment account of the multiplepayment accounts and the second payment account is different from thefirst payment account; and in response to detecting the second contact:enable display (e.g., with display enabling unit 2410), on the displayunit 2402, of a fourth user interface, wherein the fourth user interfaceincludes: the first visual indicator identifying the payment cardassociated with multiple payment accounts, and a third visual indicatoridentifying the second payment account of the multiple payment accountsof the payment card; and enable (e.g., with enabling unit 2422) theelectronic device to use the second payment account to engage in apayment transaction via the one or more wireless communication elements.

In some embodiments, the processing unit 2408 is further configured to:in accordance with a determination that the characteristic intensity ofthe first contact is below the intensity threshold, maintain enablementof the display (e.g., using display enabling unit 2410) of the firstvisual indicator without enabling display (e.g., using display enablingunit 2410), on the display unit 2402, of the second user interface.

In some embodiments, the one or more account affordances include aplurality of account affordances. In some embodiments, a visualindicator of a currently selected payment account is highlighted. Insome embodiments, detecting the second contact includes determining thata characteristic intensity of the second contact is not above anintensity threshold.

In some embodiments, the second user interface includes a paymentaccount deletion affordance, the processing unit 2408 is furtherconfigured to: detect (e.g., with detecting unit 2412) activation of thepayment account deletion affordance; and in response to detectingactivation of the payment account deletion affordance, remove (e.g.,with removing unit) the multiple payment accounts of the payment cardfrom an electronic wallet of the device.

In some embodiments, the payment account deletion affordance includesone or more visual characteristics differentiating the payment accountdeletion affordance from the payment account selection affordance.

In some embodiments, the processing unit 2408 is further configured to:while displaying, on the display unit, the fourth user interface: detect(e.g., with detecting unit 2412) a swipe input on the touch-sensitivesurface unit 2404; and in response to detecting the swipe input, enabledisplay (e.g., with display enabling unit 2410), on the display unit2402, of a fifth user interface, wherein the fifth user interfaceincludes a fourth visual indicator identifying a second payment carddifferent from the payment card.

In some embodiments, the first user interface, the second userinterface, the third user interface, and the fourth user interface areuser interfaces of a single electronic wallet application, the singleelectronic wallet application including a plurality of payment accountsassociated with a user of the electronic device.

In some embodiments, the processing unit 2408 is further configured to:receive (e.g., with receiving unit 2420) a request for accountinformation from a contactless payment terminal; and in response toreceiving the request for account information, transmit (e.g., withtransmitting unit 2424), via the one or more wireless communication unit2406, account information for the second payment account to thecontactless payment terminal, wherein the account information enablesthe contactless payment terminal to engage in a payment transaction.

The operations described above with reference to FIG. 15 are,optionally, implemented by components depicted in FIGS. 1A-1B, FIG. 5B,or FIG. 24 . For example, receiving operation 1502, displaying operation1506, and enabling operation 1508 may be implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIG.1A-1B or 5B.

In accordance with some embodiments, FIG. 25 shows an exemplaryfunctional block diagram of an electronic device 2500 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2500 are configured to perform the techniques described above.The functional blocks of the device 2500 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 25 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 25 , a first electronic device 2500 includes: a displayunit 2502, one or more wireless communication unit 2504, and aprocessing unit 2506 coupled to the display unit 2502 and the one ormore wireless communication unit 2504.

The processing unit 2506 is configured to: receive (e.g., with receivingunit 2510) a first request to link a payment account associated with apayment card to the first electronic device; in response to receivingthe first request, initiate (e.g., with initiating unit 2512) a processfor linking the payment account to the first electronic device; aftersuccessfully linking the payment account to the first electronic device,enable concurrent display (e.g., with display enabling unit 2508), onthe display unit 2502, of: an indication that the payment account hasbeen successfully linked to the first electronic device; and aselectable affordance for linking the payment account to a secondelectronic device different from the first electronic device; andreceive (e.g., with receiving unit 2510) activation of the selectableaffordance; and in response to receiving activation of the selectableaffordance, initiate (e.g., with initiating unit 2512) a process forlinking the payment account to the second electronic device.

In some embodiments, the second electronic device is uniquely pairedwith the first electronic device.

In some embodiments, the first electronic device is paired with thesecond electronic device and the first electronic device is paired witha third electronic device, and wherein a pairing relationship betweenthe first electronic device and the second electronic device isdifferent than a pairing relationship between the first electronicdevice and the third electronic device.

In some embodiments, initiating (e.g., with initiating unit 2512) theprocess for linking the payment account to the second electronic deviceincludes: transmitting (e.g., with transmitting unit 2514), via the oneor more wireless communication elements, to a financial institutionassociated with the payment card an indication that the secondelectronic device is uniquely paired with the first electronic device.

In some embodiments, the processing unit 2506 is further configured to:after initiating linking the payment account to the second electronicdevice, receive (e.g., with receiving unit 2510) a confirmation from thesecond electronic device that linking the second electronic device tothe payment account was successful; and wherein a primary account numberlinked to the second electronic device for the payment account isdifferent from a primary account number linked to the first electronicdevice for the payment account.

In some embodiments, the first request to link a payment accountincludes an account number of the payment card and wherein initiatingthe process for linking the payment account to the second electronicdevice occurs without requiring additional input of the account numberof the payment card.

In some embodiments, a second request includes a security code of thepayment card.

In some embodiments, the processing unit 2506 is further configured to:initiate (e.g., with initiating unit 2512) the process for linking thepayment account to the second electronic device.

In some embodiments, to initiate (e.g., with initiating unit 2512) aprocess linking the payment account to the second electronic device, theprocessing unit 2506 is further configured to: transmit (e.g., withtransmitting unit 2514), via the one or more wireless communication unit2504, to a financial institution associated with the payment card: theaccount number of the credit card; and a security token confirming thepayment account was previously linked to the first electronic device.

In some embodiments, initiating the process for linking the paymentaccount to the second electronic device includes: determining whetherfurther verification is needed to link the payment account to the secondelectronic device; in accordance with a determination that furtherverification is not needed to link the payment account to the secondelectronic device, initiating a process for linking the payment accountto the second electronic device and providing an indication that thepayment account has been linked to the second electronic device; and inaccordance with a determination that further verification is needed tolink the payment account to the second electronic device, providing anindication that further verification is needed to link the paymentaccount to the second electronic device.

In some embodiments, the indication that further verification is neededto link the payment account to the second electronic device includes avisual indication of additional steps to be taken by a user to link thepayment account to the respective device.

In some embodiments, the processing unit 2506 is further configured to:transmit (e.g., with transmitting unit 2514) account linking informationto the second electronic device, wherein the account linking informationenables the second electronic device to link the payment account to thesecond electronic device.

In some embodiments, the processing unit 2506 is further configured to:in accordance with the determination that further verification is neededto link the payment account to the respective device: enable display(e.g., with display enabling unit 2508), on the display unit 2502, of aplurality of communication method affordances, wherein eachcommunication method affordance is associated with a respectivecommunication method for a verification communication; and wherein theplurality of communication method affordances is based on communicationreceived from the financial institution.

In some embodiments, the processing unit 2506 is further configured to:in accordance with the determination that further verification is neededto link the payment account to the second electronic device: receive(e.g., with receiving unit 2510) a selection of a communication methodaffordance of the plurality of communication method affordances; inresponse to receiving the selection of the communication methodaffordance, transmit (e.g., with transmitting unit 2514), to thefinancial institution, an indication of the respective communicationmethod of the selected communication method affordance; and wherein theverification communication is based on the communication methodaffordance.

In some embodiments, the processing unit 2506 is further configured to:receive (e.g., with receiving unit 2510) a primary account number fromthe financial institution for use in authorizing payments from thepayment account using the second electronic device, wherein the primaryaccount number is different than the account number of the credit card;and assign (e.g., with assigning unit 2516) the primary account numberto the respective device.

In some embodiments, an electronic wallet of the second electronicdevice includes payment account information for a second payment accountassociated with a user of the second electronic device, wherein thesecond payment account is distinct from the payment account.

In some embodiments, the processing unit 2506 is further configured to:receive (e.g., with receiving unit 2510), from the second electronicdevice, an indication that the second electronic device participated ina payment transaction using the linked payment account.

The operations described above with reference to FIG. 17 are,optionally, implemented by components depicted in FIGS. 1A-1B, FIG. 5B,or FIG. 25 . For example, receiving operation 1702, initiating operation1704, and displaying operation 1706 may be implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIG.1A-1B or 5B.

In accordance with some embodiments, FIG. 26 shows an exemplaryfunctional block diagram of an electronic device 2600 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2600 are configured to perform the techniques described above.The functional blocks of the device 2600 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 26 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 26 , a first electronic device 2600 includes: a displayunit 2602 and one or more wireless communication unit 2604, and aprocessing unit 6506 coupled to the display unit 2602 and the one ormore wireless communication unit 2604.

The processing unit 2606 is configured to: enable display (e.g., withdisplay enabling unit 2608), on the display unit 2602, of apayment-account user interface for a second electronic device that isassociated with the first electronic device, wherein enabling display ofthe payment-account user interface includes enabling concurrent displayof: a representation of a first payment account along with statusinformation for the first payment account indicating that the firstpayment account is linked to the second electronic device and that thesecond electronic device is configured to enable payment using the firstpayment account; and a representation of a second payment account alongwith status information for the second payment account indicating thatthe second payment account is linked to the first electronic device butis not linked to the second electronic device.

In some embodiments, the status information for the first paymentaccount further indicates that the first payment account is linked tothe first electronic device.

In some embodiments, the payment-account user interface includesrepresentations of one or more accounts that are associated with a userof the electronic device and that are not linked to the first electronicdevice and that are not linked to the second electronic device.

In some embodiments, the payment-account user interface includes alinking affordance associated with the second payment account, andwherein the processing unit 2606 is further configured to: detect (e.g.,with detecting unit 2610) activation of the linking affordance; and inresponse to detecting activation of the linking affordance, enabledisplay (e.g., with display enabling unit 2608), on the display unit2602, of a user interface for linking the second payment account to thesecond electronic device including a synchronization option tosynchronize payment notifications between the first electronic deviceand the second electronic device; and detect (e.g., with detecting unit2610) activation of the synchronization option; and in response todetecting activation of the a synchronization option, synchronize (e.g.,with synchronizing unit 2612) future payment notifications to bepresented at both the first electronic device and the second electronicdevice.

In some embodiments, enabling display of the payment-account userinterface includes enabling concurrent display of: a first group of afirst plurality of representations of payment accounts that are linkedto the second electronic device and not linked to the first electronicdevice; and a second group of a second plurality of representations ofpayment accounts that are linked to the first electronic device and notlinked to the second electronic device.

In some embodiments, the payment-account user interface includes alinking affordance associated with the second payment account, andwherein the processing unit 2606 is further configured to: detect (e.g.,with detecting unit 2610) activation of the linking affordance; inresponse to detecting activation of the linking affordance, enabledisplay (e.g., with display enabling unit 2608), on the display unit2602, of a user interface for linking the second payment account to thesecond electronic device; and while displaying, on the display unit2602, the user interface for linking the second payment account to thesecond electronic device, receive (e.g., with receiving unit 2614) arequest to initiate linking the second payment account to the secondelectronic device, wherein the request to initiate linking the secondpayment account to the second electronic device does not include aninput of an account number of the second payment account.

In some embodiments, the payment-account user interface includes asecond linking affordance associated with the first payment account, andwherein the first payment account is not linked to the first electronicdevice, and wherein the processing unit 2606 is further configured to:detect (e.g., with detecting unit 2610) activation of the second linkingaffordance; in response to detecting activation of the second linkingaffordance, enable display (e.g., with display enabling unit 2608), onthe display unit 2602, of a user interface for linking the first paymentaccount to the first electronic device; and while displaying, on thedisplay unit 2602, the user interface for linking the first paymentaccount to the first electronic device, receive (e.g., with receivingunit 2614) a request to initiate linking the first payment account tothe first electronic device, wherein the request to initiate linking thefirst payment account to the first electronic device does not include aninput of an account number of the first payment account.

In some embodiments, the first electronic device is a handheld deviceand the second electronic device is a wearable device.

In some embodiments, the first electronic device is a handheld deviceand the second electronic device a personal computing device that islarger than the first electronic device.

In some embodiments, the payment-account user interface for the secondelectronic device that is associated with the first electronic devicefurther includes: a representation of a third payment account along withstatus information for the third payment account indicating that thethird payment account is linked to a third electronic device and thatthe third electronic device is configured to enable payment using thethird payment account, wherein the third electronic device is differentfrom the first electronic device and the second electronic device.

The operations described above with reference to FIG. 19 are,optionally, implemented by components depicted in FIGS. 1A-1B, FIG. 5B,or FIG. 26 . For example, displaying operation 1902 may be implementedby event sorter 170, event recognizer 180, and event handler 190. Eventmonitor 171 in event sorter 170 detects a contact on touch-sensitivedisplay 112, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether a first contact at a firstlocation on the touch-sensitive surface corresponds to a predefinedevent or sub event, such as activation of an affordance on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 may utilize orcall data updater 176 or object updater 177 to update the applicationinternal state 192. In some embodiments, event handler 190 accesses arespective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIG. 1A-1B or 5B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve thedelivery to users of invitational content or any other content that maybe of interest to them. The present disclosure contemplates that in someinstances, this gathered data may include personal information data thatuniquely identifies or can be used to contact or locate a specificperson. Such personal information data can include demographic data,location-based data, telephone numbers, email addresses, home addresses,or any other identifying information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todeliver targeted content that is of greater interest to the user.Accordingly, use of such personal information data enables calculatedcontrol of the delivered content. Further, other uses for personalinformation data that benefit the user are also contemplated by thepresent disclosure.

The present disclosure further contemplates that the entitiesresponsible for the collection, analysis, disclosure, transfer, storage,or other use of such personal information data will comply withwell-established privacy policies and/or privacy practices. Inparticular, such entities should implement and consistently use privacypolicies and practices that are generally recognized as meeting orexceeding industry or governmental requirements for maintaining personalinformation data private and secure. For example, personal informationfrom users should be collected for legitimate and reasonable uses of theentity and not shared or sold outside of those legitimate uses. Further,such collection should occur only after receiving the informed consentof the users. Additionally, such entities would take any needed stepsfor safeguarding and securing access to such personal information dataand ensuring that others with access to the personal information dataadhere to their privacy policies and procedures. Further, such entitiescan subject themselves to evaluation by third parties to certify theiradherence to widely accepted privacy policies and practices.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof advertisement delivery services, the present technology can beconfigured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services. In another example, users can select not toprovide location information for targeted content delivery services. Inyet another example, users can select to not provide precise locationinformation, but permit the transfer of location zone information.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and delivered to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to thecontent delivery services, or publically available information.

What is claimed is:
 1. A first electronic device, comprising: a display;one or more processors; memory; and one or more programs stored inmemory configured to be executed by the one or more processors, the oneor more programs including instructions for: displaying, on the display,a payment-account user interface for a second electronic device that isassociated with the first electronic device, wherein displaying thepayment-account user interface includes concurrently displaying: arepresentation of a first payment account along with status informationfor the first payment account indicating that the first payment accountis linked to the second electronic device and that the second electronicdevice is configured to enable payment using the first payment account;and a representation of a second payment account along with statusinformation for the second payment account indicating that the secondpayment account is linked to the first electronic device but is notlinked to the second electronic device.
 2. The first electronic deviceof claim 1, wherein the status information for the first payment accountfurther indicates that the first payment account is linked to the firstelectronic device.
 3. The first electronic device of claim 1, whereinthe payment-account user interface includes representations of one ormore accounts that are associated with a user of the first electronicdevice and that are not linked to the first electronic device and thatare not linked to the second electronic device.
 4. The first electronicdevice of claim 1, wherein the payment-account user interface includes alinking affordance associated with the second payment account, the oneor more programs further including instructions for: detectingactivation of the linking affordance; and in response to detectingactivation of the linking affordance, displaying, on the display, a userinterface for linking the second payment account to the secondelectronic device including a synchronization option to synchronizepayment notifications between the first electronic device and the secondelectronic device; and detecting activation of the synchronizationoption; and in response to detecting activation of the synchronizationoption, synchronizing future payment notifications to be presented atboth the first electronic device and the second electronic device. 5.The first electronic device of claim 1, wherein displaying thepayment-account user interface includes concurrently displaying: a firstgroup of a first plurality of representations of payment accounts thatare linked to the second electronic device and not linked to the firstelectronic device; and a second group of a second plurality ofrepresentations of payment accounts that are linked to the firstelectronic device and not linked to the second electronic device.
 6. Thefirst electronic device of claim 1, wherein the payment-account userinterface includes a linking affordance associated with the secondpayment account, the one or more programs further including instructionsfor: detecting activation of the linking affordance; in response todetecting activation of the linking affordance, displaying, on thedisplay, a user interface for linking the second payment account to thesecond electronic device; and while displaying, on the display, the userinterface for linking the second payment account to the secondelectronic device, receiving a request to initiate linking the secondpayment account to the second electronic device, wherein the request toinitiate linking the second payment account to the second electronicdevice does not include an input of an account number of the secondpayment account.
 7. The first electronic device of claim 1, wherein thepayment-account user interface includes a second linking affordanceassociated with the first payment account, and wherein the first paymentaccount is not linked to the first electronic device, the one or moreprograms further including instructions for: detecting activation of thesecond linking affordance; in response to detecting activation of thesecond linking affordance, displaying, on the display, a user interfacefor linking the first payment account to the first electronic device;and while displaying, on the display, the user interface for linking thefirst payment account to the first electronic device, receiving arequest to initiate linking the first payment account to the firstelectronic device, wherein the request to initiate linking the firstpayment account to the first electronic device does not include an inputof an account number of the first payment account.
 8. The firstelectronic device of claim 1, wherein the first electronic device is ahandheld device and the second electronic device is a wearable device.9. The first electronic device of claim 1, wherein the first electronicdevice is a handheld device and the second electronic device a personalcomputing device that is larger than the first electronic device. 10.The first electronic device of claim 1, wherein the payment-account userinterface for the second electronic device that is associated with thefirst electronic device further includes: a representation of a thirdpayment account along with status information for the third paymentaccount indicating that the third payment account is linked to a thirdelectronic device and that the third electronic device is configured toenable payment using the third payment account, wherein the thirdelectronic device is different from the first electronic device and thesecond electronic device.
 11. A non-transitory computer-readable storagemedium comprising one or more programs configured to be executed by oneor more processors of a first electronic device with a display, the oneor more programs including instructions for: displaying, on the display,a payment-account user interface for a second electronic device that isassociated with the first electronic device, wherein displaying thepayment-account user interface includes concurrently displaying: arepresentation of a first payment account along with status informationfor the first payment account indicating that the first payment accountis linked to the second electronic device and that the second electronicdevice is configured to enable payment using the first payment account;and a representation of a second payment account along with statusinformation for the second payment account indicating that the secondpayment account is linked to the first electronic device but is notlinked to the second electronic device.
 12. A method, comprising: at afirst electronic device with a display: displaying, on the display, apayment-account user interface for a second electronic device that isassociated with the first electronic device, wherein displaying thepayment-account user interface includes concurrently displaying: arepresentation of a first payment account along with status informationfor the first payment account indicating that the first payment accountis linked to the second electronic device and that the second electronicdevice is configured to enable payment using the first payment account;and a representation of a second payment account along with statusinformation for the second payment account indicating that the secondpayment account is linked to the first electronic device but is notlinked to the second electronic device.